ADTRAN R13.12.1 Release Notes 24-Port Gigabit Switch Instruction Manual

R13.12.1 Release Notes 24-Port Gigabit Switch

ADTRAN Operating System
R13.12.1 Release Notes
Release Notes
6AOSR13121-40A
February 2022

To the Holder of this Document
The contents of this manual are current as of the date of publication. ADTRAN reserves the right to change the contents without prior 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.
Be advised that certain security risks are inherent in the use of any telecommunications or networking equipment, including but not limited to, toll fraud, Denial of Service (DoS) attacks, loss or theft of data, and the unauthorized or illegal use of said equipment. ADTRAN OFFERS NO WARRANTIES, EITHER EXPRESSED OR IMPLIED, REGARDING THE PREVENTION, DETECTION, OR DETERRENCE OF TOLL FRAUD, NETWORKING ATTACKS, OR  UNAUTHORIZED, ILLEGAL, OR IMPROPER USE OF ADTRAN EQUIPMENT OR SOFTWARE. THEREFORE, ADTRAN IS NOT LIABLE FOR ANY LOSSES OR DAMAGES RESULTING FROM SUCH FRAUD, ATTACK, OR  IMPROPER USE, INCLUDING, BUT NOT LIMITED TO, HUMAN AND DATA PRIVACY, INTELLECTUAL PROPERTY, MATERIAL ASSETS, FINANCIAL RESOURCES, LABOR AND LEGAL COSTS. Ultimately, the responsibility for  securing your telecommunication and networking equipment rests with you, and you are encouraged to review documentation regarding available security measures, their configuration and implementation, and to test such features as is  necessary for your network.

Introduction

AOS version R13.12.1 is a maintenance release that addresses customer issues 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 Community, https://supportcommunity.adtran.com. The contents of these release notes will focus on the platforms listed in “Supported Platforms” on page 4. Additional information specific to AOS, and the products supported in this release, is outlined in “System Notes” on page 12.

Supported Platforms

Table 1 lists the platforms that are supported in AOS version R13.12.1. 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 (email support@adtran.com or call 888-423-8726) for assistance.
Table 1. Supported Platforms

Platform| Standard Feature Pack| Enhanced Feature Pack| SBC Feature Pack| Minimum
Boot ROM
---|---|---|---|---
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
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 900 Series (3rd Gen.)| | | | R13.7.0.B1
Total Access 900e Series (3rd Gen.)| | | | R10.9.0

Features and Enhancements

General Features in R13.12.0
This section highlights the major features, commands, and behavioral changes for all products running AOS version R13.12.0.

• Upgraded OpenSSL to 1.1.1i.
• Increased the maximum number of tracks from 1,000 to 1,020.
• Introduced support for GRE over IPsec on the NetVanta 3148 and 4148.
• Added the ability to disable key exchange algorithms, MAC algorithms, and ciphers on the SSH server. Additionally, the diffie-hellman-group1-sha1 key exchange algorithm, hmac-sha1 MAC algorithm, and 3des-cbc cipher are now  disabled by default.

Voice Features in R13.12.0
This section highlights the major voice related features, commands, and behavioral changes for all products running AOS version R13.12.0.

• Added support for RTCP multiplexing on SIP to SIP calls through the B2BUA.

Fixes

General Bug Fixes in R13.12.1
This section highlights major bug fixes for all products running AOS version R13.12.1.

• Fixed an issue in which a reboot may have occurred when using TACACS+.

• Fixed an issue in which AOS continued to send IPv6 Router Solicitations after
  MAX_RTR_SOLICITATIONS (in violation of RFC 4861 section 6.3.7) if an IPv6 Router Advertisement had not been received.

• Added QoS map counters to the adGenAosQoS MIB that were present in the CLI but missing from the MIB.

• Fixed an issue in which IPv6 Neighbor and Router Solicitations were sent 40 seconds after an interface came up, even if an IPv6 Router Advertisement had been received. This violated RFC 4861.

General Bug Fixes in R13.12.0
This section highlights major bug fixes for all products running AOS version R13.12.0.

• Fixed an issue in which navigating to the QoS maps page in the GUI of a NetVanta 3148 or 4148 would cause the GUI to become unresponsive until the unit was rebooted.
• Fixed an issue in which IRT_DEFAULT was set to 600 seconds instead of 86400 seconds as specified in RFC 8415 section 7.6.
• Fixed an issue on the NetVanta 3148 and 4148 in which throughput between routed interfaces and switch ports was poor.
• Added the sysObjID for the NetVanta 4148 without PoE (P/N 17004148F1) to the adtrantc MIB.

Voice Specific Bug Fixes in R13.12.1
This section highlights voice specific bug fixes in AOS version R13.12.1.

• Fixed an issue in which the rtcp-mux attribute was advertised in SDP for TDM-to-SIP calls when RTCP was disabled.

Voice Specific Bug Fixes in R13.12.0
This section highlights voice specific bug fixes in AOS version R13.12.0.

• Fixed an issue in which SIP requests would be sent to the wrong server if deregistration from the previously selected server failed after a successful server rollover when using validated SIP registration.
• Fixed an issue in which a reboot would occur if local ringback generation was triggered and the received INVITE did not contain a SDP offer.
• Fixed an issue in which a local 3-way conference was not established properly if a remote SIP UA replied to a reINVITE initiating a conference with a SDP answer containing hold SDP.
• Fixed an issue in which SDP generation failed when using SIP over TCP with no sip udp configured.
• Fixed an issue in which RFC 3680 subscriptions may have been initiated to a server with which the device was not registered.
• Fixed an issue in which received SIP UPDATE requests were improperly rejected on early dialogs.
• Fixed an issue in which a SIP registration state track would enter the failed state if deregistration from the previously selected server failed after a successful server rollover when using validated SIP registration.
• Fixed an issue in which SIP server monitor failed to generate properly formatted SIP messages when the selected server had an IPv6 address.
• Fixed an issue in which a reboot may have occurred in rare cases if HMR was configured.
• Fixed an issue in which a SIP dialog was not formed upon a successful RFC 3680 subscription.
• Fixed an issue in which multiple Authorization or Proxy-Authorization headers may have been included in SIP requests. This issue was introduced in R13.9.0.
• Fixed an issue in which FXS ports would ring indefinitely if a MGCP SignalRequest for L/r6 or L/r7 was received.
• Fixed an issue in which configuring an empty voice codec-list resulted in no codecs being displayed in subsequent codec-lists.
• Fixed an issue in which SIP resources were leaked during nonce processing during authentication. Over time, this leak would result in the unit being unable to send SIP REGISTER requests. This issue was introduced in AOS R13.9.0
• Fixed an issue in which SIP server TLS certificate validation failed if the CA certificate for validating external servers was not the first listed CA certificate in the CA profile.
• Fixed an issue in which SIP SUBSCRIBE requests sent in response to an authentication challenge may not have included the authorization header.

Switch Specific Bug Fixes in R13.12.1
This section highlights voice specific bug fixes in AOS version R13.12.1.

• Fixed an issue on the NetVanta 1550 in which a reboot could occur if the RSTP packet pool was depleted.

Errata

General Errata
The following is a list of errata that exists in all products running AOS version R13.12.1.

• On the NetVanta 3148 and 4148, the output of the show power inline command lists 12 gigabit switch ports instead of 8.

• A reboot may occur when running line rate traffic on the NetVanta 3148 and 4148 through an interface that has an access-policy assigned that contains discard entries.

• On the Total Access 900 Third Generation, a remote payload loopback initiated from the DSX interface (t1 0/2) does not function properly.

• On the Total Access 900 Third Generation, the Network (t1 0/1) and DSX (t1 0/2) interfaces transmit B8ZS coded signals when configured for AMI coding.

• 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 fastallow-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 namedprefix 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

• When using the Novatel USB 551L modem with a NetVanta 3140, a small amount of lost frames will occur with packets smaller than 512 bytes. The loss occurs in the modem and not the NetVanta 3140.

• 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.

• 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 if the interface is up. This issue does not affect the NetVanta 4660, 5660, or 6360. A  workaround is to 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 on MEF Ethernet interfaces in show running-config verbose command output, even though those options are not valid or configurable 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. Also, when the cursor hovers over a data point, it displays multiple instances of the same data.

• 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 may hang with a Please Wait message.

• The output of show qos map interface command displays ce-vlan-id instead of vlan-id, and ce-vlan-pri instead of cos, on products other than the NetVanta 4660, 5660, and 6360.

• SFP information for an SFP inserted into a NetVanta 4430 does not display correctly.

• Ethernet interfaces in 3rd generation Total Access 900e products cannot be seen from the Data > IP Interfaces menu in the GUI. Workaround: Configure these interfaces from the System > Physical Interfaces menu instead.

• The 3rd generation Total Access 900e 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 module can stop negotiating LCP when part of an MLPPP bundle. Rebooting the device will restore the interface.

• On a NetVanta 6310, if a SHDSL circuit with a detected bad splice retrains to a different line rate, the distance of the bad splice will display incorrectly.

• 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.

• On the NetVanta 6310 and 6330, the T1 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 reset. 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 displays Tracked by: Nothing in the show probe command output. This is only 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.

• 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 AccessRequest 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.12.1.

• 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 for Layer 2 services 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.12.1.

• When using SRTP with mandatory SIP TLS, unattended transfers may fail with an error that states: Cannot establish call over unsecure transport.
• When using SIP TLS in client-server mode with the firewall enabled, if the firewall removes the policy session for an idle established inbound SIP TLS connection, the SIP TLS session won’t get cleared by the SIP stack. Over time,  this can result in all 24 available SIP TLS connections being consumed, preventing the unit from initiating or accepting new SIP TLS connections until it is rebooted.
• A local 3-way conference will not be established properly if a remote SIP UA replies to a reINVITE initiating a conference with an SDP answer containing hold SDP.
• When using RTCP multiplexing on only one side of a SIP to SIP call, the remote host listed for the RTCP session in the output of show rtp media sessions may be listed incorrectly.
• 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.
• 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.
• The clear sip tls session command does not function.
• 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 Accessclass 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 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 sixty 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.
• Receiving a 183 after a 183 on hairpin calls when using media anchoring could 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.12.1

• PoE+ devices that require negotiation via LLDP MDI TLV will not be powered by NetVanta 1638 switches configured in ActivChassis mode.
• Shutting down a switchport with a connected SFP Interconnect cable on a NetVanta 1544F may not properly shutdown the interface.
• 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.
• 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.

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.12.1 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.12.1 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 online at https://supportcommunity.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)

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://supportcommunity.adtran.com.

Warranty and Contact Information

Warranty information can be found online by visiting www.adtran.com/warranty.
To contact ADTRAN, choose one of the following methods:

Department| Contact Information|
---|---|---
Customer Care| From within the U.S.:
From outside the U.S.:| (888) 4ADTRAN ((888)-423-8726)+
+1 256-963-8716
Technical Support| Support Community
Product Support:| supportcommunity.adtran.com
www.adtran.com/support
Training| Email:
ADTRAN University:| training@adtran.com
www.adtran.com/training
Sales| For pricing and availability:| 1 800-827-0807

901 Explorer Boulevard
P.O. Box 140000
Huntsville, AL 35814-4000
Phone: 256-963-8000
Copyright © 2022 ADTRAN, Inc.
All Rights Reserved.

References

• Home - Adtran Support Community
• Support
• Training
• My Adtran Log In
• Warranty Information
• Support Center
• Home - Adtran Support Community
• AOS Command Reference Guide - Adtran Support Community
• Upgrading Firmware in AOS - Adtran Support Community
• Home - Adtran Support Community
• Upgrading Firmware in AOS - Adtran Support Community
• AOS Command Reference Guide - Adtran Support Community
• Home - Adtran Support Community
• Training

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>