Adtran 834-5 SDG PlumeOS Instruction Manual

: June 12, 2024
: ADTRAN

Table of Contents

Introduction
Supported Platforms
System Notes
Features and Enhancements
Fixes
Errata
Upgrade Instructions
Restoring the Factory Defaults
Warranty and Contact Information
To the Holder of this Document
Trademark Information
Disclaimer of Liability
Customer Support
References
Read User Manual Online (PDF format)
Download This Manual (PDF format)

Adtran 834-5 SDG PlumeOS

Adtran 834-5 SDG PlumeOS

Introduction

The PlumeOS 2.2.0.2 firmware release for Adtran’s Service Delivery Gateway (SDG) products is a maintenance release that addresses customer issues uncovered in previous code releases.

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

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.

Supported Platforms

Table 1 lists the platforms that are supported in Adtran’s SDG 2.2.0.2 PlumeOS release.

Table 1. Supported Platforms

Platform

841-t6
834-5
834-v6
854-6
854-v6

NOTE

Mosaic Device Manager (MDM) customers must ensure that ACS instances are updated with the latest drivers.

System Notes

The following are important notes about the PlumeOS 2.2.0.2 release:

PlumeOS PPPoE will not work without an ACS to push down the credentials.
All PlumeOS devices running DHCP code are supported on the PlumeOS Auto Update server.
For any devices being managed on the PlumeOS Auto Update Server, they will be updated to PlumeOS 2.2.0.2 in the upcoming weeks (refer to the PlumeOS Auto Update Feature for 841-t6 article for more information). For upgrade notifications, subscribe to the PlumeOS 841-t6 Auto-Update Software Notifications board in the Adtran Support Community.
The 841-t6 does not support SSH connections unless it is currently connected to the Plume Cloud.
If a device running PlumeOS is unable to connect to the cloud for more than 10 consecutive minutes, it will reboot due to an OpenSync Health Check (as do other OpenSync devices).

Features and Enhancements

Features and Enhancements in 2.2.0.2

There are no new features introduced in the PlumeOS 2.2.0.2 maintenance release.

Features and Enhancements in 2.2.01

This section highlights features and enhancements included in the PlumeOS 2.2.0.1 release.

Regional support with DFS included in this release. Some regions are determined based off of the part number of the device, as they were manufactured for that specific region. When loading firmware on these devices, the device firmware will evaluate the device part number and apply the correct power settings for your regional regulations. New Zealand and Canada require a separate cusdef build since they do not have separate part numbers. The information below outlines the version you must run for each region.
- United States: plos-sdg-mkt-arm-2.2.0.1.run
- United Kingdom (GB): plos-sdg-mtk-arm-2.2.0.1.run
- EU: plos-sdg-mkt-arm-2.2.0.1.run
- Australia: plos-sdg-mtk-arm-2.2.0.1.run
- Canada: plos-sdg-mtk-arm-2.2.0.1-regdom-ca.run
- New Zealand: plos-sdg-mtk-arm-2.2.0.1-regdom-nz.run
PPPoE support is included in the plos-sdg-mtk-arm-2.2.0.1-generic-pppoe.run software. PPPoE is supported on the 834-5, 834-v6, and 854-(v)6 SDG devices in Router mode only. PPPoE use also requires the use of an ACS and uses generic PPPoE credentials.
SDGP-232 Enhanced power level for specific licensed customers in Canada.
SDGP-230 Introduced a TR-069 parameter to control SSH access capability

Fixes

General Bug Fixes in 2.2.0.2

This section highlights major bug fixes in the PlumeOS 2.2.0.2 release.

PLOS-1291 Fixed an issue in which, in some cases, devices could still be accessed via IPv4 even when a PlumeOS router had firewall rules in place to deny access.
PLOS-1448 Fixed an issue in which, in some cases, devices configured as extenders would reset repeatedly due to Internet health check failures.
PLOS-1452 Fixed an issue in which, when connecting extenders to an existing network, routing could be briefly disrupted.

General Bug Fixes in 2.2.0.1

This section highlights major bug fixes in the PlumeOS 2.2.0.1 release.

PLOS-341 Fixed an issue in which there could be a 10 minute delay before DHCP discovery was accessible and traffic could pass through LAN ports on the 841-t6.
PLOS-381 Fixed an issue in which multiple LAN clients could not saturate the 2.5G link fully with traffic.
PLOS-490 Enabled MUMIMO DL.
PLOS-573 Fixed an issue in which reboots caused by Watchdog events were not properly logged in Plume.
PLOS-664 Fixed an issue in which multiple DNS queries to the same address were seen due to the DNS cache not being properly enabled in an 841-t6 operating as an extender.
PLOS-690 Fixed an issue in which some 854-6 devices could be identified as 854-v6 devices in TR-069.
PLOS-889 Fixed an issue in which some logpull commands would fail.
PLOS-897 Fixed an issue in which logpull did not include osp_reboot_reason.
PLOS-919 Fixed an issue in which a router may hand down IPv6 IA_PD lifetimes that did not match upstream lifetimes.
PLOS-920 Fixed an issue in which a router could hand down IPv6 IA_NA lifetimes of infinity.
PLOS-922 Fixed an issue in which a unit acting as a router would not pass the upstream IPv6 IA_NA preferred timers down via DHCPv6.
PLOS-934 Fixed an issue in which Sig Fault errors could appear in the Frontline Reboot Timeline when using an 841 as a wired extender, or connecting an 841 to a wired switch.
PLOS-935 Fixed an issue in which, in some cases, devices could crash without properly populating logpulls.
PLOS-936 Fixed an issue in which some 834-v6 SDG devices would not display a DIAGNOSTIC_COMPLETE event in the Event Logs while rebooting after triggering NPT.
PLOS-941 Fixed an issue in which the help text for the upgrade protocol command in the admin CLI was in all uppercase letters, although the command had to be entered in lowercase letters only.
PLOS-948 Fixed an issue in which networks with multiple daisy-chained extenders or a PlumeOS router being simultaneously upgraded could cause downstream 841-t6 upgrades to timeout.
PLOS-959 Fixed an issue in which connectivity issues between the 841-t6 and a connected gateway could intermittently cause failed optimizations.
PLOS-1013 Fixed an issue which some SDG devices would not operate properly due to erroneously being assigned global IPv6 addresses.
PLOS-1017 Fixed an issue in which the network monitor process could intermittently fail.
PLOS-1121 Fixed an issue in which 841-t6 devices could send IPv6 Router Advertisements on the WAN port, causing loops in the network.
PLOS-1125 Fixed an issue in which, if a wired link between an 841-t6 acting as an extender and another OpenSync device was bouncing, a network loop was created when the device switched over to wireless backhaul.
PLOS-1137 Fixed an issue in which the timezone setting via DHCP would not correctly adjust the time offset from UTC time for FCC testing.
PLOS-1144 Fixed an issue in which SNR was being reported to the Plume Cloud incorrectly, causing the Plume health checks to report parallel WiFi networks.
PLOS-1145 Fixed an issue in which crash reporting was not always accurate in Plume Frontline’s Reboot Timeline.
PLOS-1171 Fixed an issue in which devices could take approximately 30 minutes to come online in the Plume Cloud after upgrading with PPPoE.
PLOS-1250 Fixed an issue in which devices behind a PlumeOS router could still be accessed via IPv6
PLOS-1267 Fixed an issue in which CM crashes on SDG devices could intermittently occur, causing all devices on the network to shut down.
PLOS-1282 Fixed an issue in which duplicate IP addresses could conflict with routers using the 192.168.1.1 IP address.
PLOS-1285 Fixed an issue in which certain process executions could crash the 841-t6 device.
PLOS-1288 Fixed an issue in which the PPPoE username and password were not preserved with some device upgrades.

Errata

The following is a list of errata that still exist in the PlumeOS 2.2.0.2 release.

PLOS-339 Some devices may not be band-steered properly on an 841-t6.
PLOS-401 The Bluetooth beacon MAC address may not match the unit’s base MAC address. This will not affect Home Pass or Frontline; they will display the correct MAC address.
PLOS-672 Wired links between PlumeOS mesh units will not show up in Frontline. They will instead appear as a separate gateway.
PLOS-709 IPv6 throughput is limited to 80% of the IPv4 throughput maximums in the unit.
PLOS-960 In some situations, devices will send Pause Frames in cases of bursty traffic, even when Pause Frames have not been negotiated on the Ethernet port. Repeated speed tests (20 or more in a row) can lead to a state where speed test performance from the unit, or through the unit, is significantly degraded.
PLOS-961 In rare cases, clients are unable to connect to a radio that has switched to a DFS channel.
PLOS-1146 Download throughput on the 834-5 5 GHz radio, when operating with 80 MHz channels, may show low throughput. LAN to Wireless throughput will be expected.
PLOS-1475 In some cases, wired and wireless loops can be created when using 854 or 841 wired extenders.

Upgrade Instructions

Upgrading Adtran’s SDG products to the latest version of software is outlined in the following sections.

Step 1: Upgrading Firmware

PlumeOS software for the 834-5, 834-v6, and 854-(v)6 must be managed via TR-69 upgrades. For information on performing the upgrade via Mosaic Device Manager (MDM), refer to the Updating Firmware article included in the MDM online help for specific instructions.

The 841-t6 running PlumeOS can be upgraded via ACS, but is also included by default in the PlumeOS Auto Update Service and will be periodically updated. Refer to the PlumeOS Auto Update Feature for 841-t6 article in the Adtran Support Community for more information. To receive upgrade notifications, subscribe to the PlumeOS 841-t6 Auto-Update Software Notifications board, also in the Adtran Support Community.

Step 2: Verifying the Version

SDG software versions can be verified either via the ACS or by using the Plume Frontline tool. Instructions for both methods are provided in this section.

Verifying Software Version Using the ACS

To verify the SDG software version using the ACS, follow these steps:

Log into the ACS URL (https://smartrg.com), using your specific customer instance name and your login credentials.
Enter the device serial number (or subscriber associated with the device) into the Find Subscriber or Device search bar and select the magnifying glass to execute the search.
Once the device is located, select the device link to open the Device page. The Firmware Version is displayed in the middle of the menu.

Verifying Software Version Using Plume Frontline

To verify the SDG software version using Plume Frontline, follow these steps:

Access the Frontline tool by entering the following address in your browser https://portal.plume.com/home, and then log in using your login credentials.
Navigate to the Applications menu, and select Frontline Tier 1. In the resulting search bar, enter your Plume account or node ID (for example, device@customer.com).
Once the account page is displayed, select Pods and Nodes from the menu on the left.
In the Pods and Nodes menu, locate your specific pod and you can view your Firmware Vers directly under the Device Type (as shown in the image below).

Restoring the Factory Defaults

To restore the factory default settings to your device, press and hold the Reset button on the device for 30 seconds. Do not hold the button for longer than 55 seconds, as that will cause the device to roll back to the last bootable firmware version.

A factory reset can also be performed from the Admin CLI with the command factory-reset, or it can be sent from the ACS via TR-069.

Warranty and Contact Information

Warranty information can be found online by visiting www.adtran.com/en/about- us/legal.

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:| www.supportcommunity.adtran.com
www.adtran.com/en/aboutus/support
Training| Email:
Adtran University| training@adtran.com
www.adtran.com/en/productsandservices/services/training
Sales| For pricing and availability:| 1 800-827-0807

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.