Copyright Information
©Copyright 2021 Hewlett Packard Enterprise Development LP.
Open Source Code
This product includes code licensed under the GNU General Public License, the GNU Lesser General Public License, and/or certain other open source licenses. A complete machine-readable copy of the source code corresponding to such code is available upon request. This offer is valid to anyone in receipt of this information and shall expire three years following the date of the final distribution of this product version by Hewlett Packard Enterprise Company. To obtain such source code, send a check or money order in the amount of US $10.00 to: Hewlett Packard Enterprise Company, 6280 America Center Drive, San Jose, CA 95002, USA.
Notices
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All third-party marks are property of their respective owners.
Description
NetEdit provides automation of search, edit, validation, deployment, and audit for network configurations. It provides intelligent assistance and continuous validation to help ensure that device configurations are consistent, compliant, and error free. NetEdit can be used without retraining, by leveraging your existing knowledge and experience with switch configuration. This enables you to automate switch configuration change workflows without programming.
For additional details, see the latest Aruba NetEdit datasheet located at Aruba NetEdit Datasheet.
Version History
All released versions are fully supported by Hewlett Packard Enterprise, unless noted in the table.
| Version number | Release date | Remarks |
|---|---|---|
| 2.1.1 | 2021-08-13 | Released, fully supported, and posted to the web. |
| 2.1.0 | 2021-04-16 | Released, fully supported, and posted to the web. |
| 2.0.12 | 2021-02-08 | Released, fully supported, and posted to the web. |
| 2.0.11 | 2020-12-15 | Released, fully supported, and posted to the web. |
| 2.0.10 | 2020-11-06 | Released, fully supported, and posted to the web. |
| 2.0.9 | 2020-09-25 | Released, fully supported, and posted to the web. |
| 2.0.8 | 2020-08-21 | Released, fully supported, and posted to the web. |
| 2.0.6 | 2020-07-17 | Released, fully supported, and posted to the web. |
| 2.0.5 | 2020-06-10 | Released, fully supported, and posted to the web. |
| 2.0.4 | 2020-05-08 | Released, fully supported, and posted to the web. |
| 2.0.3 | 2020-03-03 | Released, fully supported, and posted to the web. |
| 2.0.2 | 2020-02-04 | Released, fully supported, and posted to the web. |
| 2.0.1 | 2019-12-19 | Released, fully supported, and posted to the web. |
| 2.0 | 2019-12-06 | Released, fully supported, and posted to the web. |
| 1.1.1 | 2019-08-20 | Released, fully supported, and posted to the web. |
| 1.1 | 2019-05-06 | Released, fully supported, and posted to the web. |
| 1.0 | 2018-12-18 | Initial release of NetEdit software. Released, fully supported, and posted to the web. |
Important Information
This section contains important information about NetEdit. Administrators will not be able to run some network-related utilities on the OVA as they may not have been installed or were made unavailable to harden the system from probes or attacks. For example, ping is only available to root so users on the system cannot probe the network with ping.
When discovering a device with any of the following properties:
- Loopback IP address configured
- Route-only-port IP address on the connected interface
- SVI IP address on the connected interface
the device will not be discovered by NetEdit. In order to use a device's OOBM IP address to discover the device with any of these properties the LLDP management address will need to be configured on the device before attempting discovery from NetEdit. This can be accomplished by running the following command from the device CLI: lldp management-ipv4-address <IP-ADDR>
Devices Supported
Installation of this release enables support for the following devices:
| Product number | Description |
|---|---|
| JL479A | Aruba 8320 48p 10G SFP/SFP+ and 6p 40G QSFP+ with X472 5 Fans 2 Power Supply Switch Bundle |
| JL579A | Aruba 8320 32p 40G QSFP+ with X472 5 Fans 2 Power Supply Switch Bundle |
| JL581A | Aruba 8320 48p 1G/10GBASE-T and 6p 40G QSFP+ with X472 5 Fans 2 Power Supply Switch Bundle |
| JL624A | Aruba 8325-48Y8C 48p 25G SFP/+/28 8p 100G QSFP+/28 Front-to-Back 6 Fans and 2 PSU Bundle |
| JL625A | Aruba 8325-48Y8C 48p 25G SFP/+/28 8p 100G QSFP+/28 Back-to-Front 6 Fans and 2 PSU Bundle |
| JL626A | Aruba 8325-32C 32-port 100G QSFP+/QSFP28 Front-to-Back 6 Fans and 2 Power Supply Bundle |
| JL627A | Aruba 8325-32C 32-port 100G QSFP+/QSFP28 Back-to-Front 6 Fans and 2 Power Supply Bundle |
| JL375A | Aruba 8400 8-slot Chassis/3xFan Trays/18xFans/Cable Manager/X462 Bundle |
| JL376A | Aruba 8400 1x Mgmt Mod 3x PS 2x 8400X Fabric Mod 1x 32p 10G Mod and 1x 8p 40G Mod Bundle (includes JL375A) |
| JL658A | Aruba 6300M 24-port SFP+ and 4-port SFP56 Switch |
| JL661A | Aruba 6300M 48-port 1GbE PoE Class 4 and 4-port SFP56 Switch |
| JL662A | Aruba 6300M 24-port 1GbE PoE Class 4 and 4-port SFP56 Switch |
| JL663A | Aruba 6300M 48-port 1GbE and 4-port SFP56 Switch |
| JL664A | Aruba 6300M 24-port 1GbE and 4-port SFP56 Switch |
| JL762A | Aruba 6300M 48-port 1GbE and 4-port SFP56 Switch |
| JL665A | Aruba 6300F 48-port 1GbE PoE Class 4 and 4-port SFP56 Switch |
| JL666A | Aruba 6300F 24-port 1GbE PoE Class 4 and 4-port SFP56 Switch |
| JL667A | Aruba 6300F 48-port 1GbE and 4-port SFP56 Switch |
| JL668A | Aruba 6300F 24-port 1GbE and 4-port SFP56 Switch |
| JL675A | Aruba 6100 48G Class4 PoE 4SFP+ 370W Switch |
| JL676A | Aruba 6100 48G 4SFP+ Switch |
| JL677A | Aruba 6100 24G Class4 PoE 4SFP+ 370 Switch |
| JL678A | Aruba 6100 24G 4SFP+ Switch |
| JL679A | Aruba 6100 12G Class4 PoE 2G&2SFP+ 139W Switch |
| JL724A | Aruba 6200F 24G 4SFP+ Switch |
| JL725A | Aruba 6200F 24G Class4 PoE 4SFP+ 370W Switch |
| JL726A | Aruba 6200F 48G 4SFP+ Switch |
| JL727A | Aruba 6200F 48G Class4 PoE 4SFP+ 370W Switch |
| JL728A | Aruba 6200F 48G Class4 PoE 4SFP+ 740W Switch |
| R0X26A | Aruba 6405 Switch |
| R0X27A | Aruba 6410 Switch |
| JL700A | Aruba 8360-32Y4C with MACSec Port to Power 3 Fans 2 PSU Bundle |
| JL701A | Aruba 8360-32Y4C with MACSec Power to Port 3 Fans 2 PSU Bundle |
| JL702A | Aruba 8360-16Y2C Port to Power 3 Fans 2 PSU Bundle |
| JL703A | Aruba 8360-16Y2C Power to Port 3 Fans 2 PSU Bundle |
| JL706A | Aruba 8360-48XT4C Port to Power 3 Fans 2 PSU Bundle |
| JL707A | Aruba 8360-48XT4C Power to Port 3 Fans 2 PSU Bundle |
| JL708A | Aruba 8360-12C Port to Power 3 Fans 2 PSU Bundle |
| JL709A | Aruba 8360-12C Power to Port 3 Fans 2 PSU Bundle |
| JL710A | Aruba 8360-24XF2C Port to Power 3 Fans 2 PSU Bundle |
| JL711A | Aruba 8360-24XF2C Power to Port 3 Fans 2 PSU Bundle |
| JL817A | Aruba 4100i 12-port 1GbE (8-port Class 4 POE and 4-port Class 6 POE) 2-port SFP+ DIN Mount Switch |
| JL818A | Aruba 4100i 24-port 1GbE (20-port Class 4 POE and 4-port Class 6 POE) 4-port SFP+ Switch |
The topology view can display 3rd party devices to ensure network visibility. NetEdit will not manage 3rd party devices.
Compatibility and Interoperability
NetEdit server requirements (VMWare)
Ability to deploy the NetEdit OVA to a vSphere ESXi Server environment (version 6.0 or higher) with:
- 6 CPUs
- 32 GB RAM
- 115 GB disk space (initial size 2.5 GB when thin provisioned)
- A network with connectivity to the target switches to be managed
NetEdit server requirements (Hyper-V)
- 6 CPUs
- 32 GB RAM
- 115 GB disk space (initial size 2.5 GB when thin provisioned)
- A network with connectivity to the target switches to be managed
- Windows Server 2019 or later
NetEdit client-side requirements
A supported browser with network connectivity to the NetEdit server. Supported browsers:
| Browser | Minimum supported version |
|---|---|
| Chrome | 69 |
| Firefox | 56 |
Enhancements
This section lists enhancements added to this branch of the software. Software enhancements are listed in reverse-chronological order, with the newest on the top of the list. Unless otherwise noted, each software version listed includes all enhancements added in earlier versions.
Version 2.1.1
Updated to support the 10.08.0001, 10.07.0020, and 10.06.0140 release of AOS-CX. This version also includes support for sub-interfaces.
Version 2.1.0
Updated to support the 10.07.0001 and 10.06.0110 releases of AOS-CX. Version 2.1.0 includes the following key enhancements:
- TACACS
- CSV Device Import
- Aruba Fabric Composer Integration
- NAE Deployment
Version 2.0.12
Updated to support the 10.04.3060, 10.05.0050, and 10.06.0100 releases of AOS-CX. If an unknown command is found during the NetEdit check of command syntax, NetEdit now prompts to allow you to override the error/warning and validate the configuration with the switch. If switch validation succeeds, the configuration can successfully be deployed to the switch.
Version 2.0.11
Updated to support the 10.04.3050, 10.05.0040, and 10.060010 releases of AOS-CX and the Aruba 6100 Switch Series.
Version 2.0.10
Updated to support the 10.04.3031, 10.05.0021, and 10.06 releases of AOS-CX and the Aruba 8360 Switch Series.
Version 2.0.9
No enhancements were included in version 2.0.9.
Version 2.0.8
A warning message has been added detailing what NetEdit can do with regards to VSF stack configuration.
Version 2.0.6
Updated to support the 10.05.0001 release of AOS-CX.
Version 2.0.5
Updated to support the 10.04.3000 release of AOS-CX.
Version 2.0.4
Updated to support AOS-CX 10.04.2000, the Aruba 6410 Switch, and the Aruba 6200 Switch Series. Version 2.0.4 also includes the following key enhancements:
- Hyper-V support
- Multiple quality enhancements
Version 2.0.3
Updated to support AOS-CX 10.04.1000 and the Aruba 6200 Switch series. Version 2.0.3 includes the following key enhancements:
- DC Spine Leaf Solution
- Multiple quality enhancements
Version 2.0.2
This version only contains bug fixes. There are no new feature enhancements.
Version 2.0.1
This version only contains bug fixes. There are no new feature enhancements.
Version 2.0
Updated to support AOS-CX 10.04 and the Aruba 6300 & 6400 Switch series. Version 2.0 includes the following key enhancements:
- Network Topology UI
- CX Subscription-driven Topology
- Topology Health Layers:
- Application
- Client Service
- Segmentation
- Routing
- Bridging
- Device
- Aruba Network Analytics Engine (NAE) Status Aggregation
- External Notifications:
- Slack
- TopDesk
- Service Now
- Graphical Multi-switch Solution Configuration
Fixes
This section lists released builds that include fixes found in this branch of the software. Software fixes are listed in reverse-chronological order, with the newest on the top of the list. Unless otherwise noted, each software version listed includes all fixes added in earlier versions. The Symptom statement describes what a user might experience if this is seen on the network. The Scenario statement provides additional environment details and trigger summaries. When available, the Workaround statement provides a workaround to the issue for customers who decide not to update to this version of software. The Bug ID is used for tracking purposes.
Version 2.1.1
| Category | Bug ID | Description |
|---|---|---|
| Topology | 4789 | Symptom: The topology view page becomes unresponsive. Scenario: When a topology with more than 400 devices is discovered, the topology view page becomes unresponsive. |
| Topology | 4856 | Symptom: LAG information in the Topology page takes longer than expected to display. Scenario: After making changes to the LAG interface for discovered devices, the information takes longer than expected to display in the Topology page. Workaround: Reload the page or navigate away and come back to the Topology page. |
Version 2.1.0
| Category | Bug ID | Description |
|---|---|---|
| Deployment | 4508 | Symptom: The device stays in the 'deploying' state indefinitely, unable to be added to a new firmware plan. Scenario: When deploying firmware to a device, if a 'not qualified for deployment' error message is displayed, the device may sometimes stay in the 'deploying' state indefinitely and be unable to be added to a new firmware plan. |
| Device discovery | 4659 | Symptom: A device shows as 'unreachable' in NetEdit. Scenario: When discovering an Aruba 6300 VSF stack in NetEdit, the device will show as 'unreachable' in NetEdit. |
| Device discovery | 4429 | Symptom: Unexpected network traffic related to discovery polling is seen. Scenario: After disabling discover on the Settings page, network traffic related to discovery polling is seen. |
| Logs | 4512 | Symptom: Log flooding fills up the disk on the NetEdit OVA, preventing the user from logging in. Scenario: When the NetEdit log is run excessively, log flooding fills the disk where the NetEdit OVA resides. Workaround: Rotate the logs. |
| MultiEditor | 4569 | Symptom: Password complexity rules are not enforced. Scenario: When creating a new user with a complex password using the MultiEditor, the password complexity rules are not enforced. Workaround: Use the switch CLI to create new users with complex passwords. |
| Settings | 4701 | Symptom: ISL LAG interface settings are changed unexpectedly. Scenario: When deploying a configuration change to a VSX pair, the ISL LAG interface settings are changed unexpectedly. |
Version 2.0.12
| Category | Bug ID | Description |
|---|---|---|
| Device management | 4582 | Symptom/Scenario: Some devices running AOS-Switch are not discovered or the devices are discovered and then become unreachable within five minutes. |
| Device management | 4593 | Symptom: Third party switches are not correctly discovered by NetEdit. Scenario: After discovering a third party switch, the device appears on the Device page, but device details are never completed and the busy spinner never stops spinning. |
| Device management | 4624 | Symptom: LAG details do not display in the Properties panel for the device. Scenario: When clicking a link in the Topology view that is a LAG for an AOS-CX device, no LAG details are displayed in the Properties panel. |
Version 2.0.11
| Category | Bug ID | Description |
|---|---|---|
| Installation | 4392 | Symptom: NetEdit installation fails. Scenario: When installing NetEdit for the first time on a VM that has an incorrect system time, the installation fails. Workaround: Correct the VM system time and reinstall NetEdit. |
Version 2.0.10
| Category | Bug ID | Description |
|---|---|---|
| MultiEditor | 4346 | Symptom: Syntax errors are observed in the MultiEditor. Scenario: When the line copp-policy default is added to the MultiEditor and the configuration is deployed to the switch, syntax errors are displayed in the MultiEditor. Workaround: Use the switch CLI to configure copp-policy default. |
Version 2.0.9
| Category | Bug ID | Description |
|---|---|---|
| Deployment | 4499 | Symptom: The ntp.conf file unexpectedly contains the default NTP pool. Scenario: After configuring a custom NTP server, the ntp.conf file still contains the default NTP pool, rather than the newly configured pool. Workaround: Manually edit the ntp.conf file to remove the default pool entry. |
Version 2.0.8
| Category | Bug ID | Description |
|---|---|---|
| MultiEditor | 4356 | Symptom: Deployment of a configuration with TACACS/RADIUS server commands fails. Scenario: When TACACS/RADIUS servers are included in a configuration and deployed by the MultiEditor, deployment to the switch succeeds but NetEdit sometimes reports it as a failure if the TACACS/RADIUS server order changes. Workaround: Include server IP addresses in sorted order (ascending octets) or do not use MultiEditor to deploy the configuration. For example, if the following servers (192.168.10.10, 192.168.9.10 ) are to be defined in the config, they should be entered in the following order 192.168.9.10, 192.168.10.10. |
| MultiEditor | 4516 | Symptom: BGP neighbor commands fail validation in MultiEditor. Scenario: When BGP neighbor commands containing neighbor names with the hyphen (-) or underscore (_) character are included in MultiEditor, the commands fail validation. Workaround: Remove the commands from the plan or remove the hyphen and/or underscore characters from the neighbor names. |
Version 2.0.6
| Category | Bug ID | Description |
|---|---|---|
| Discovery | 4337 | Symptom/Scenario: After import, the device shows up as managed and unreachable. Workaround: Disable and re-enable the port to which the device is connected. |
| Firmware deployment | 4454 | Symptom: The firmware file upload to the NetEdit server times out on low bandwidth connections. Scenario: With lower uplink speeds (<10 Mbps), or when rate-limit is set to lower speeds, an upload of AOS-CX firmware to the NetEdit server may time out since the current default timeout is five minutes. |
| MultiEditor | 4450, 4480 | Symptom: Certain commands are marked with a red line in the MultiEditor. Scenario: When adding certain commands to a plan using the MultiEditor, the commands are marked with a red line and are not recognized. Workaround: Use the CLI to add these commands. |
| Validation | 4456 | Symptom: A device is marked as unreachable immediately after discovery. Scenario: When a device has UBT included in the config before adding it to NetEdit, the device will be marked as unreachable immediately after discovery. Workaround: Disable or remove UBT configuration from the device prior to adding it to NetEdit. |
Version 2.0.5
| Category | Bug ID | Description |
|---|---|---|
| Deployment | 4396 | Symptom: The no preempt command is ordered after the exit command, causing an error and prohibiting deployment. Scenario: In certain circumstances, adding a setting to a port configuration causes the preempt command to be ordered after the exit command in the configuration, which prohibits deployment of the configuration. |
| MultiEditor | 4385 | Symptom: The aaa accounting port-access start-stop interim 5 group clearpass command appears incorrectly in the MultiEditor. Scenario: On a device running AOS-CX 10.04.2000, when the aaa accounting port-access start-stop interim 5 group clearpass command is entered into the MultiEditor, MultiEditor removes the space character between the 5 and word group, resulting in a command that displays as aaa accounting port-access start-stop interim 5group clearpass. Workaround: This is cosmetic only and does not effect validation or deployment of the config. |
Version 2.0.4
| Category | Bug ID | Description |
|---|---|---|
| Deployment | 4372 | Symptom: NetEdit fails to flag a warning for QOS Schedule profile configuration in the MultiEditor. Scenario: When the QoS policy is applied to individual interfaces in a LAG, rather than to the LAG, the policy does not get assigned to the interface without NetEdit raising a warning. |
Version 2.0.3
| Category | Bug ID | Description |
|---|---|---|
| Discovery | 4373 | Symptom: A Cisco 3560 shows as unreachable. Scenario: After a successful discovery by NetEdit, a Cisco 3560 shows as unreachable, even though it is reachable. The netedit.log confirms an SNMP fingerprint was retrieved. |
| MultiEditor | 4380 | Symptom: Validation fails for the vrf attach vsxdpd command on an Aruba 6400 Switch Series switch. Scenario: The vrf attach vsxdpd command is accepted by a 6405 switch at the command line, but fails validation when applied in the MultiEditor. |
| Validation | 4384 | Symptom: The system interface-group command is flagged as invalid by NetEdit. Scenario: After discovering an Aruba 8400 switch with an Aruba 8400X-32Y 32p 1/10/25G SFP/SFP+/SFP28 Module (JL687A) line card installed, the system interface-group command is flagged as invalid syntax and cannot be edited or added from NetEdit. For example, system interface-group 5 line-module 1/2 speed 10g is in the config at the time of discovery, but NetEdit underlines the command in yellow. |
Version 2.0.2
| Category | Bug ID | Description |
|---|---|---|
| Discovery | 4080 | Symptom: When discovery is initiated using an IP from a seed router with multiple IP addresses NetEdit may discover each IP address of the router as a separate device. Scenario: A router with multiple subnets and IP addresses is used as a discovery seed device by specifying one or more of its IP addresses. When only one IP address is specified as a seed the router may sometimes be misrepresented in NetEdit as multiple devices. This can occur because the router's other interfaces may be discovered by common methods such as LLDP, CDP, or REST neighbor data. If two or more IP addresses of such a device are specified as seeds then they will be represented as independent devices by NetEdit. NOTE: This issue should only apply to routers that are specified as seed devices. Other routers with multiple IP addresses should be correctly represented by NetEdit. Workaround: The extraneous devices can be manually identified and deleted using the NetEdit Devices view. Sorting by the Serial or MAC columns should allow the user to easily identify the misrepresented "duplicate" devices as they will have identical serial numbers and MAC addresses. The user should identify the entry that represents the preferred management IP for the device, multi-select the incorrect IP addresses, and delete them. |
Version 2.0.1
| Category | Bug ID | Description |
|---|---|---|
| Discovery | 4246 | Symptom: NetEdit displays a validation error similar to Interface X/Y/Z is not L3, % Command failed. Scenario: When a 6300 or 6400 is discovered and an attempt to configure an interface with routing with the ip mtu command, an error message similar to Interface X/Y/Z is not L3, % Command failed. displays. |
Version 2.0
| Category | Bug ID | Description |
|---|---|---|
| Attributes framework | 4121 | Symptom: NetEdit fails to launch after upgrading to version 2.0.0. Scenario: Null pointer exception while migrating the serial number of a device running ArubaOS-CX version 10.01 or earlier causes a migration script failure in NetEdit. Workaround: Deploy NetEdit version 2.0.0 as new OVA. |
| Attributes framework | 0967 | Symptom: The settings attributes table displays multiple entries with identical names. Scenario: When creating attributes, if an attribute name is created with one or more space characters at the end, duplicate entries appear on the settings attribute table. For example, Test and Test [space] both display as Test in the table. Workaround: Avoid appending the space character to the end of attribute names. |
| Dashboard | 0832 | Symptom: The dashboard page layout is unexpectedly reset to the default layout. Scenario: After customizing the dashboard layout, if a tile is enabled and/or disabled, the dashboard layout resets to the default settings. Workaround: Add and remove all tiles desired before attempting to reposition and customize the layout. |
| Device management | 0934 | Symptom: Unable to delete a device from the Devices page. Scenario: If multiple administrators are accessing the application at the same time and one administrator tries deleting a device in a plan that is being deployed by the other administrator, the device cannot be deleted. After the plan has been deployed, the device still cannot be deleted. Workaround: Wait for any deployments to finish and refresh the Devices page before attempting to delete a device. |
| Device validation | 39946 | Symptom: Device Validation reports a message similar to There is no matched command... at or near the line containing the banner command. Scenario: When using a question mark character (?) in the banner text, a message similar to There is no matched command... displays at or near the line containing the banner command. Workaround: Remove the question mark character (?) from the banner text. |
Issues and Workarounds
The following are known open issues with this version of the software. The Symptom statement describes what a user might experience if this is seen in the software. The Scenario statement provides additional environment details and trigger summaries. When available, the Workaround statement provides a workaround to the issue.
Version 2.1.1
| Category | Bug ID | Description |
|---|---|---|
| Discovery | 2711 | Symptom: A stack member is shown on the network view. Scenario: When you discover a set of devices before forming the stack, then form the stack, a stack member may be shown on the network view. Workaround: Delete the stack member that is still visible after the stack if formed. |
| Discovery | 3794 | Symptom: A deleted device connected to a non-AOS-CX device displays again immediately on the Diagnostics page. Scenario: When removing a device that is connected to a non-AOS-CX device from the network and you delete it from the network view, it may show up on the Diagnostics page. Workaround: Wait at least five minutes after taking the device offline before deleting it from the network view. |
| Firmware deployment | 40631 | Symptom: Deployment of firmware upload fails. Scenario: When attempting to upload a firmware image that is incompatible with the device, the upload fails with an error message similar to request failed 500. Workaround: Verify that the firmware image file is compatible with the device before attempting the upload. |
| MultiEditor | 0706 | Symptom: Validation errors reported for the invalid commands. Scenario: Select a command that is not valid for the configuration line being entered. Workaround: Use the validation errors reported to find the erroneous commands and enter the correct configuration lines. |
| MultiEditor | 0941 | Symptom: A notification displays in the bottom right side of the editor. Scenario: If multiple validation tasks are initiated on the same device, any subsequent requests that are invoked while the first validation is in progress produce a message that reads "Request failed with status code 429". Workaround: Wait for the first validation task to complete for a specified device before invoking any subsequent validation tasks. |
| MultiEditor | 0998 | Symptom: The editor blocks attempts to edit Networking Analytics Engine (NAE) commands and displays a warning that reads "The line is classified as read only. The line can be deleted but cannot be updated." Scenario: The entering of NAE commands (nae-script, nae-agent) in the editor are allowed even though such lines are marked as read-only after editing. Workaround: Avoid entering NAE commands in the editor outside of pasting a configuration that already includes NAE commands. |
| MultiEditor | 1054 | Symptom: MultiEditor displays a busy indicator (spinner) when starting a new MultiEdit session. Scenario: MultiEditor shows a busy indicator (spinner) while loading or modifying device configurations. Performing very large operations, such as pasting a multi-thousand line configuration into a plan with many devices, may take several minutes. During this time the busy indicator will be present. If an attempt is made to start a MultiEditor session for a different plan, the busy indicator will still be shown until the MultiEditor is able to complete the previous large operation, even if it is for a different plan. Workaround: Wait for the busy indicator to clear before starting a new MultiEditor session. |
| MultiEditor | 1118 | Symptom: The deploy process completes in the UI, but the change is not deployed. Scenario: When deploying a change which includes 15k or more lines of configuration text, the process completes bu the change is not deployed. All change validation commands indicate an error has occurred in the post-change results. Workaround: Reduce the number of lines in the switch configuration. |
| MultiEditor | 4857 | Symptom: When multiple instances of vlan protocol ... are entered, the first instance of the command is overwritten. Scenario: In the interface context, when more than four instances of the vlan protocol ... command are entered with unique tokens, the first instance of the command may be overwritten. Workaround: Use the switch CLI to add more than four VLAN protocols. |
| Network | 1138 | Symptom: The user will see a "Network Error" message if there are any communication issues. On pages with tables, the tables may show the message "No Data" if the data collection is taking a long time. The user may see a white screen when they initially access the NetEdit web UI. Scenario: The problem may occur if the customer has a slow and/or unreliable network connection. Workaround: The customer should ensure that their network connection is reliable and sufficiently fast. |
| OVA function | 1162 | Symptom: Machine on the same network as the NetEdit VM cannot get an IP address from the DHCP server. Scenario: When the NetEdit VM is configured to use a DHCP server to get its IP address and the VM experiences a disk error disallowing writes to the disk (for example. forced into read-only mode, out of disk space, and so forth), the DHCP server exhausts the list of IP addresses, causing other machines on the network to not receive an IP address. Workaround: Configure the NetEdit VM to use a static IP address. Log into the NetEdit VM as neadmin and run the netedit_config.py script to reconfigure network settings. |
| Plan management | 1245 | Symptom: Deploying large configurations results in unexpected "Running config changed" plans. Scenario: If a configuration deploy succeeds but the post configuration validation fails, this will result in the plan status being marked as "Deploy Failed'. However, since the configuration was successfully applied to the device, that configuration change will be detected by NetEdit's configuration scanning. This can result in a "Running config changed" plan being created for the devices in the "failed" plan. These "Running config changed" plans will contain the configuration changes made in the "failed" plan. This situation may occur when deploying very large configurations, deploying to devices that are under heavy load, or deploying over networks with very high latency. Workaround: If post deploy validation fails due to an intermittent cause, be aware that the successfully applied configuration may appear in a subsequent "Running config changed" plan. |
| Search | 1101 | Symptom: When using the calendar date picker for a search, the year automatically resets to "2018". Scenario: If the "Year" dropdown box is used to select a year in the calendar date picker from the search text box, the year automatically resets to "2018" after about two seconds. Workaround: Rather than using the "Year" dropdown, navigate through the months and years using the left and right arrow buttons or type the date in manually using the MM/DD/YY HH:MM format. |
Version 1.1.1
No fixes were added in version 1.1.1.
Version 1.1
| Category | Bug ID | Description |
|---|---|---|
| Change validation | 32381 | Symptom: Change Validation displays % Capacities not ready instead of meaningful data. Scenario: When using the show capacities or show capacities-status commands as part of the Change Validation feature, an error message similar to % Capacities not ready displays, rather than meaningful capacity information. Workaround: Avoid using show capacities or show capacities-status as part of the Change Validation feature. |
| Device validation | 43426 | Symptom: The scanned configuration from a switch causes Device Validation errors with respect to the lag command. Scenario: Manually removing a LAG from the CLI command shell using the no lag command results in an invalid configuration. Workaround: Avoid using the no lag command until all associated LACP configurations referencing the LAG are removed first. The lacp command can be removed in the MultiEditor after it is detected as failing Device Validation. |
| Device validation | 44073 | Symptom/Scenario: Device Validation reports as failed with no indication of which lines have failed validation. Workaround: Retry the Device Validation. |
| Logging | 1446 | Symptom: Unexpected messages display in the /var/log/syslog, /var/log/daemon.log, /var/log/auth.log, and/or /var/log/wtmp files. Scenario: When a serial port is not associated to the virtual machine, error messages such as the following can display in the various log files: /dev/ttyS0: not a tty serial-getty@ttyS0.service: Service hold-off time over, scheduling restart Stopped Serial Getty on ttyS0 Started Serial Getty on ttyS0 [6] [01345] [tyS0] [LOGIN ] [ttyS0 ] [ ] [0.0.0.0 ] [2018-07-12T06:15:37,317855+0000] Workaround: Permanently disable these messages by running the following command: sudo systemctl disable serial-getty@ttyS0.service |
Feature Caveats
| Feature | Description |
|---|---|
| Configuration | After upgrading to NetEdit to 2.1.x, a configuration change is seen for every switch in the network. This is because the led locator command was filtered in NetEdit 2.0.12 and earlier, and is not filtered in NetEdit 2.1.0 and later. |
| module command | The module command can only be used manually in the CLI command shell to prepopulate interfaces. |
| Host key checking | NetEdit disables strict host key checking in the internal Java SSH library. SSH tools outside NetEdit are not affected. |
| MultiEditor | When using a dotted decimal subnet mask format in the NetEdit MultiEditor, a syntax error will appear on the configuration line. |
| MultiEditor | When configuring a command using a range in the NetEdit MultiEditor (for example, interface vlan 2-2001), a syntax error will be shown even if the command is valid. |
| MultiEditor | During configuration of a range (such as interface 1/1/1-1/1/3 or vlan 1-10) in the MultiEditor, the command displays as an unrecognized command. |
| Reboot Device | Reboot Device is not supported for non AOS-CX devices. |
| VSF | NetEdit requires that VSF stacks be formed and most changes made using the CLI or Aruba CX mobile app. For example, adding members to a stack, deleting members from a stack, adding a new VSF link, and replacement of a member with a different SKU are not supported using NetEdit. NetEdit only supports adding a port to a VSF link, removing a port in a VSF link, removing a standby member from a VSF stack, and modifying a standby member in a VSF stack. Other changes to the VSF stack using NetEdit may lead to members rebooting and not re-joining the stack. To recover from this scenario, the configuration has to be fixed in the master or the member zeroized and added back to the stack using the CLI. |
Upgrading from Earlier Versions
Refer to the NetEdit Installation Guide for information on upgrading from earlier versions.
Downgrading to an earlier version of NetEdit is not supported.
Documentation Feedback
Aruba is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback-switching@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
