ArubaOS-CX 10.00.0010 Release Notes For The Aruba 8400 Switch Series-A00041872en - Us
ArubaOS-CX 10.00.0010 Release Notes For The Aruba 8400 Switch Series-A00041872en - Us
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.
Contents
Contents 3
LAG.................................................................................................................................... 15
Line module........................................................................................................................15
Link Aggregation................................................................................................................ 15
Loop Protection.................................................................................................................. 16
NTP.................................................................................................................................... 16
Web UI................................................................................................................................17
Version 10.00.0005....................................................................................................................... 17
BGP....................................................................................................................................17
Configuration...................................................................................................................... 17
LLDP.................................................................................................................................. 17
Loop Protection.................................................................................................................. 17
OSPF..................................................................................................................................18
sFlow.................................................................................................................................. 18
Web UI................................................................................................................................18
Version 10.00.0004....................................................................................................................... 19
Classifier.............................................................................................................................19
Loop Protection.................................................................................................................. 19
Loopback............................................................................................................................19
Management...................................................................................................................... 19
Power Supply..................................................................................................................... 20
VLAN.................................................................................................................................. 20
Web UI................................................................................................................................20
Version 10.00.0003....................................................................................................................... 20
Classifier.............................................................................................................................20
Diagnostics.........................................................................................................................20
L3 Addressing.................................................................................................................... 21
LAG.................................................................................................................................... 21
LLDP.................................................................................................................................. 21
Loop Protection.................................................................................................................. 21
NAE.................................................................................................................................... 21
OSPFv3..............................................................................................................................22
VRRP................................................................................................................................. 22
Web UI................................................................................................................................22
Issues and workarounds.......................................................................................................................... 22
ARP...............................................................................................................................................22
CR_25306.......................................................................................................................... 22
CR_25334.......................................................................................................................... 22
Jumbo Frames.............................................................................................................................. 23
CR_25546.......................................................................................................................... 23
L3 Addressing............................................................................................................................... 23
CR_12008.......................................................................................................................... 23
CR_23936.......................................................................................................................... 23
LAG............................................................................................................................................... 23
CR_24779.......................................................................................................................... 23
Multicast........................................................................................................................................ 23
CR_22901.......................................................................................................................... 23
CR_23498.......................................................................................................................... 23
NAE...............................................................................................................................................24
CR_24268.......................................................................................................................... 24
OSPF............................................................................................................................................ 24
CR_08491.......................................................................................................................... 24
VRRP............................................................................................................................................ 24
CR_24910.......................................................................................................................... 24
Feature caveats............................................................................................................................ 24
Upgrade information................................................................................................................................ 25
File transfer methods.................................................................................................................... 26
Enabling the management port.......................................................................................... 26
Chapter 3 Websites........................................................................................ 31
Contents 5
Chapter 1
ArubaOS-CX 10.00.0010 Release Notes
Description
This release note covers software versions for the ArubaOS-CX 10.00 branch of the software.
If you run the show version command on the 8400, the version number will display XL.10.00.xxxx,
where xxxx is the minor version number.
ArubaOS-CX is a new, modern, fully programmable operating system built using a database-centric design that
ensures higher availability and dynamic software process changes for reduced downtime. In addition to robust
hardware reliability, the ArubaOS-CX operating system includes additional software elements not available with
traditional systems, including the features included in the Enhancements section of this release note.
Version 10.00.0001 was the initial build of major version 10.00 software.
Product series supported by this software:
Important information
To avoid damage to your equipment, do not interrupt power to the switch during a software update.
Version history
All released versions are fully supported by Hewlett Packard Enterprise, unless noted in the table.
Table Continued
Products supported
This release applies to the following product models:
Compatibility/interoperability
The switch web agent supports the following web browsers:
Firefox (Ubuntu) 52
The following table provides information on compatibility of the switches found in this release note with network
management software:
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 10.00.0010
No enhancements were included in version 10.00.0010.
Version 10.00.0009
Version 10.00.0009 was never built.
Version 10.00.0008
No enhancements were included in version 10.00.0008.
Version 10.00.0007
VLAN names
Support was added for the space character to be used in VLAN naming.
Version 10.00.0006
Hardware support
Support for the Aruba 8400X 6-port 40GbE/100GbE QSFP28 Advanced Module (JL366A) has been added.
MCLAG
Added MCLAG support with IGMP within a VLAN.
OSPF
Support for OSPF MD5 authentication for interfaces and virtual links has been added. This can be configured
using the key-id parameter in the CLI command ip ospf message-digest-key <id> md5 cyphertext
<key>.
Version 10.00.0004
ACLs
New CLI options ([interface <ID> [{in|out}]]) were added to display ACL statistics for a specific
interface. If multiple ACLs are applied to an interface, the statistics for each ACL is displayed. The syntax of the
show access-list hitcounts command is now the following:
show access-list hitcounts {ip|ipv6|mac} <ACL-NAME> [interface <ID> [{in|out}]]
For example:
SNMP
The following MIBs to support CPU and memory utilization have been added:
Temperature
New event logging messages were added to indicate the line module has exceeded the temperature threshold
(Over temperature for sensor <SENSOR-NAME>, <TEMP> C) and when the line module is about to be
shut down by the system (Module <ID> shutdown initiated for sensor <SENSOR-NAME>, <TEMP>
C). LED indicators on the front of the chassis have also been modified to flash orange to help indicate the
temperature issue exists.
Version 10.00.0003
No enhancements were included in version 10.00.0003.
Version 10.00.0002
Checkpoint configuration management
Makes it easy to manage and roll back configurations, including automatic rollback in case of network failure. The
built-in database acts as a network record, enabling support for multiple configuration checkpoints and the ability
to roll back to a previous configuration checkpoint.
Layer 3 ARP
IP datagram forwarding
IP options
TCP (RFC 793)
UDP (RFC 768)
ICMP
IPv6 ND
IPv6 FIB
Layer 3 routing interface
VRF Lite
• Static route
• OSPF
• BGP
IPv6 routing:
Table Continued
Table Continued
Security RADIUS
TACACS+
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 number that precedes the fix description is used for tracking purposes.
Version 10.00.0010
No fixes were included in version 10.00.0010.
Version 10.00.0009
Version 10.00.0009 was never built.
Version 10.00.0008
Console
CR_27420
Symptom: Unexpected messages are displayed on the switch console.
Scenario: After issuing the boot system command, the switch may randomly display unexpected messages on
the switch console, similar to [FAILED] Failed unmounting /run/netns.
Workaround: None. These messages do not have any impact to the switch or protocol functionality.
DHCPv6
CR_29827
Symptom: Network clients are not able to obtain an IPv6 address from some DHCPv6 servers.
Scenario: When the switch is configured as a DHCPv6 relay agent, network clients may not be able to obtain an
IPv6 address from some DHCPv6 servers.
SNMP
CR_29892
Symptom/Scenario: When running multiple and repetitive SNMP queries, the switch memory utilization may
increase over time.
Workaround: If observed switch memory utilization increasing over time, disable the SNMP agent on the switch
using the no snmp-service vrf mgmt | default command and then re-enable the agent using the snmp-
service vrf mgmt | default command.
Spanning Tree
CR_29754
Symptom: The switch incorrectly places ports in "blocking" state.
Scenario: In an MSTP configuration, if an event (such as disabling or disconnecting a port) is causing a topology
change, switch ports may be incorrectly placed in "blocking" state, potentially causing two switches to become
root and preventing the spanning-tree topology from properly converging. When this condition happens, the
received and sent BPDU counters do not match in the output of the show spanning-tree detail command.
Workaround: Rebooting the switch will clear the incorrect port status and allow the spanning tree topology to
properly converge.
Version 10.00.0007
ARP
CR_28891
Symptom: In certain conditions, the switch experiences traffic loss.
Scenario: In a switch configured in an MCLAG topology with VRRP, when there is a MAC or ARP aging event or
when the events are cleared using the clear mac-address [ port | vlan ] <PORTNAME | VLAN-ID>
or clear arp commands, the switch may experience traffic drops.
Workaround: Reboot the switch.
BGP
CR_22531
Symptom: Unable to remove the password for a BGP neighbor.
Scenario: When attempting to remove the BGP neighbor password using the no neighbor <ip-address>
password <password-string> command, the configured password is not removed.
Workaround: Remove the <password-string> from the command, using just no neighbor <ip-
address> password.
CR_22993
Symptom: A route that should be denied per the AS path filter list is being permitted.
Scenario: A denied route in the AS path list is selected as best route in the BGP table when the routemap has a
permit rule.
Workaround: Add a deny rule to the route map to filter out the route.
VLAN
CR_28993
Symptom/Sceanario: The switch fails to display the active-gateway configuration in the output of the show
running-config interface <IFNAME> command.
Workaround: Use the show running-config command to display the active-gateway configuration for the
VLAN interfaces.
Version 10.00.0006
Classifier
CR_28817
Symptom: The switch incorrectly allows the user to configure a policy action for PCP remarking.
Scenario: Although the switch does not support policy action for PCP remarking, the CLI configuration is not
correctly rejected.
Workaround: Do not use PCP remarking with a policy action.
Console
CR_29108
Symptom: The switch terminates all active sessions to the switch.
Scenario: When using show commands, the switch may abruptly terminate the active session to the switch.
Workaround: Use the specific interface ID show command, show interface <interface_id>.
LAG
CR_28392
Symptom/Scenario: Switch fails to display the configured description for the LAG interface in the output of the
show running-config command.
Workaround: Reconfigure the description on the interface.
Line module
CR_29090
Symptom/Scenario: Under certain conditions, the switch ports appear in a "waiting for link" state.
Link Aggregation
CR_28992
Symptom: A switch port does not successfully come up.
Scenario: When a switch port which is a member of a LAG interface with an ACL applied is moved to another
LAG interface, the port fails to come up in the new LAG interface.
Loop Protection
CR_27347
Symptom: The switch sends the incorrect event severity level for loop detection messages.
Scenario: The switch sends the syslog messages for loop detection as informational instead of warning
messages.
Workaround: Consider the loop detection message as having a warning level, rather than an info level.
CR_27387
Symptom: The switch does not correctly display the loop detection.
Scenario: When loop protection action is configured for do-not-disable, the switch fails to update the loop
detection status in the output of the show loop-protect command. For example:
Interface 1/1/1
Loop-protect enabled : Yes
Action on loop detection : Do not disable
Loop detected count : 0
Loop detected : No
Interface status : up
NTP
CR_29252
Symptom: The switch line cards crash after execution of the show ntp status command.
Scenario: When the switch is configured with an NTP server and the switch time is subsequently manually
changed using CLI commands, it may cause a software abort error in the dune-agent and the switch line modules
entering an endless reboot cycle. The switch will generate event logs similar to
systemd-coredump|1201|LOG_CRIT|LC|1/1|dune_agent_0 crashed due to signal:6
hpe-cardd|3207|LOG_ERR|AMM|1/5|Line module 1/1 has failed: ASIC Error
hpe-cardd|3207|LOG_ERR|AMM|1/5|Line module 1/1 has failed: ASIC Error
Workaround: Perform the following:
Version 10.00.0005
BGP
CR_22984
Symptom/Scenario: When configuring peer-group route-reflector-client, the BGP sessions belonging to a peer-
group do not get automatically reset.
Workaround: Use the clear ip bgp peer-group <peer-group> command to clear the BGP sessions.
CR_25819
Symptom: The AS number is displayed as zero.
Scenario: The output of the show ip bgp summary command is incorrect when the neighbor is assigned to
the peer-group without configuring a remote AS neighbor.
Workaround: Configure the neighbor's remote AS before assigning to the peer-group.
Configuration
CR_27983
Symptom: A switch with a configuration file out of the box may fail to correctly apply the added configuration.
Scenario: When the switch configuration is created on top of the original configuration file that is on the switch
management module out of the box, the switch may fail with any of the following symptoms:
Workaround: Zeroize the switch management module before additional configuration is added to the switch
using the erase all zerioze command in the config context.
LLDP
CR_25313
Symptom: SNMP traps are not working.
Scenario: If the trap server is running on the management VRF, SNMP traps do not work.
Workaround: Run the SNMP server on the default VRF.
Loop Protection
CR_27349
Symptom: Switch cannot enable loop protection on some interfaces.
interface 1/1/24
no routing
vlan trunk allowed all
loop-protect vlan 1000
interface lag1
vlan allowed all
loop-protect
Workaround: Have specific VLANs in the allowed list and then enable loop protection.
CR_27376
Symptom: In certain conditions, the switch may not properly detect network loops.
Scenario: When loop protection is enabled on an interface, the switch does not properly detect the network loops
generated in the network segment connected on that switch interface.
Workaround: This issue is specific to switches running ArubaOS-Switch as the loop pair. Identify the redundant
link and disable the alternate path.
OSPF
CR_25468
Symptom: OSPF interface statistics are not accurate with overlapping IP addresses across VRFs.
Scenario: If the same IP addresses are used on more than one VRF, then the OSPFv2 statistics are updated
only on one VRF.
Workaround: Use only non-overlapping IP addresses under different VRFs.
CR_17335
Symptom: Virtual link is not functioning as expected.
Scenario: Virtual link may not function as expected if the remote end is initially configured to be area 0 and later
changed to a different area.
Workaround: Avoid area ID changes "on the fly". You can reboot the switch to solve the issue, if needed.
sFlow
CR_25865
Symptom: sFlow sampling will not work when line modules are in non-consecutive slots.
Scenario: If there is a gap between line modules, sFlow sampling will only work on the lowest numbered module
before the gap. For example, if slots 1, 3, and 4 have line modules installed, but slot 2 does not, sFlow sampling
will only work on the ports on line module 1.
Workaround: Install line modules in contiguous order starting at slot 1.
Web UI
CR_26451
Symptom/Scenario: When using the Firefox browser, a dialog box reporting an error on attempt to upload new
firmware is displayed.
Workaround: When seeing this dialog, user needs to log out and clear the cache in the browser, then try to log in
again and reattempt the upload. To clear cache, enter URL: about:preferences, then type cache in the
search. Select Clear Now button to clear cache.
Loop Protection
CR_27096
Symptom: Loop protection may not be enabled on all VLANs.
Scenario: Switch fails to enable loop protection on all VLANs using the CLI command loop-protect vlan
all in the interface context.
The switch also returns an error message similar to VLAN <VLAN-ID> is not configured on the
interface when enabling loop-protect on an interface where all VLANs are allowed.
Example:
interface <INTF-NAME>
no routing
vlan trunk allowed all
loop-protect vlan <VLAN-ID>
Workaround: Use a VLAN range to enable loop-protect on all VLANs, such as loop-protect vlan
<1-4094>.
Loopback
CR_23416
Symptom: An error string is shown in the event log about invalid command no shutdown for the loopback
interface.
Scenario: The loopback interface displays no shutdown in the running configuration; however, the shutdown
and no shutdown commands are not available for the loopback interface. This results in error messages when
importing the configuration to the switch. This error can be ignored and will not impede importing the configuration
file.
Workaround: This is a display issue only, with no functional impact.
Management
CR_22122
Symptom/Scenario: When running snmpwalk, the entPhysicalVendorType is not correctly updated.
Workaround: Use the following CLI commands to find out the vendor information.
show system
show module
CR_26986
Symptom/Scenario: Out of the box, OOBM and SSH are enabled. After factory reset, the OOBM port and the
SSH server are disabled.
Power Supply
CR_25480
Symptom: PSU insert shows input fault state and blinking green LED.
Scenario: When a PSU is hot inserted or re-inserted into slot, PSU shows blinking green LED and the show
environment power-supply command displays input fault.
Workaround: Remove the PSU and wait 5-10 seconds before re-inserting.
VLAN
CR_26840
Symptom: Line modules are rebooted causing momentary traffic loss until the modules are back in a "Ready"
state.
Scenario: When a VLAN which has IGMP snooping enabled gets deleted without removing the IGMP snooping
configuration, all the line modules see a fatal error and get rebooted.
Workaround: Before deleting the VLAN, un-configure IGMP snooping on the VLAN.
Web UI
CR_27066
Symptom/Scenario: Incorrect serial numbers for switch components may be displayed in the System Info widget
of the Overview web page of the Web UI.
Workaround: Use the show module command to display the correct serial numbers.
CR_27323
Symptom: The switch fails to update the switch image version.
Scenario: After uploading a new switch image version using the Web UI Firmware Update page, the switch fails
to update the information on the Web UI page.
Workaround: Use the browser Refresh button to refresh the information displayed on the Firmware Update page.
Version 10.00.0003
Classifier
CR_25894
Symptom: Switch may fail to honor a "drop" policy action.
Scenario: When a rate-limit and drop action are combined in a single policy, the switch fails to honor the drop
action.
Workaround: Configure separate policies for drop and rate-limit actions.
Diagnostics
CR_26016
Symptom: Switch may fail to display the diagnostic information for some line modules.
Scenario: Switch may fail to display the diagnostic information such as memory or CPU for some line modules.
An error message similar to System resource utilization data not available displays when using
the show system resource-utilization module <MODULE-ID> command.
L3 Addressing
CR_26915
Symptom: A LAG IP address may not be correctly programmed.
Scenario: If the IP address is assigned to a LAG interface before assigning port members to the LAG interface,
the LAG IP address may not be correctly programmed when the line module is reloaded or after a system reboot.
Workaround: Remove and re-assign the IP address to the LAG interface.
LAG
CR_26265
Symptom: A LAG interface may enter a blocked state.
Scenario: When all line modules are removed and reinserted, a LAG interface status may show blocked in the
output of the show lacp interfaces command.
Workaround: Reload the module with the affected LAG interface using the boot line-module <MODULE-ID>
command.
LLDP
CR_26559
Symptom: LLDP MIB does not display Port Description values.
Scenario: Network Management Systems fail to retrieve port description information from LLDP MIB.
Workaround: Use the show lldp neighbor-info command to check neighbor details..
Loop Protection
CR_26766
Symptom: The switch may fail to re-enable an interface disabled by loop protection.
Scenario: When the loop protection timer is configured on an interface, the switch fails to re-enable the interface
after consecutive disable/enable triggers on the interface due to loop detections.
Workaround: Once the loop is removed, manually enable the interface using the no shutdown command from
the interface context.
NAE
CR_25443
Symptom: Network Analytics Engine (NAE) allows for empty parameter values to be present. The NAE user
interface does not correctly display this particular case properly, and you may see red colored error text when
editing a parameter that indicates that the value is missing or invalid; however, you can ignore it and continue to
save edited parameters. The UI also does not display default values specified in the Python script while editing an
agent. Empty parameters display red error text, indicating that the value is missing or invalid when it is in fact
valid.
Scenario: When a script with empty parameter values is created and instantiated via REST and then the agent is
edited in the UI, NAE displays red error text, indicating a value is missing or invalid, when it really is valid.
Workaround: The issue is visual only, you can save the agent without changing any parameter values, or cancel
updating the agent.
VRRP
CR_25532
Symptom: SNMP traps are not working.
Scenario: If the trap server is running on the management VRF, SNMP traps do not work.
Workaround: Run the SNMP server on the default VRF.
Web UI
CR_24166
Symptom: The web UI displays a timeout error if the request takes more than 60 seconds to complete.
Scenario: When using the web UI to perform various operations, a timeout error may be displayed if the request
takes more than 60 seconds to complete. One example of this is trying to copy one configuration to another (i.e.
copy a configuration to startup-config).
Workaround: Do one of the following:
1. Wait a few minutes and check the status of the operation to see if it was actually successful. For example,
when updating the configuration, after a couple of seconds, on refreshing the page, the new startup config
(which was requested to be copied over) can be seen with the updated time.
2. Use the CLI.
ARP
CR_25306
Symptom: IPv6 neighbor entry is updated with the wrong VLAN.
Scenario: When multiple parallel L3 links exist between the same physical neighbors, the IPv6 neighbor entry is
updated with the wrong VLAN.
Workaround: Use L2 LAGs with SVI or L3 LAGs between the same physical neighbors.
CR_25334
Symptom: Total number of neighbors is greater than the configured cache limit.
Jumbo Frames
CR_25546
Symptom: Traffic larger than configured MTU is dropped.
Scenario: When packet size is bigger than the configured egress interface MTU, packets are not fragmented and
thus dropped.
Workaround: Configure the MTU on the egress interface such that fragmentation will not occur.
L3 Addressing
CR_12008
Symptom/Scenario: The switch does not send out RA Packets with lifetime=0 values before rebooting.
Workaround: Do one of the following:
CR_23936
Symptom: IPv6 RA is not advertised by the device.
Scenario: IPv6 RA is not advertised when configuring more than 120 VLANs with 8 IPv6 prefixes assigned to
each VLAN.
Workaround: Limit the IPv6 RA-enabled VLAN below 120.
LAG
CR_24779
Symptom: LAG assignments across multiple VRFs are impacted following configuration replay from a saved
checkpoint with port-vrf assignment configurations.
Scenario: LAG assignments across multiple VRFs are retained even though the VRFs were deleted and the
startup configuration was copied to the running configuration.
Workaround: Reboot the switch after the configuration from a checkpoint has been restored.
Multicast
CR_22901
Symptom/Scenario: When deleting an interface with a PIM-RP configuration, the RP-Candidate configuration
remains.
Workaround: Remove the RP configuration prior to deleting the interface.
CR_23498
Symptom/Scenario: Configuring a default static route for all subnets causes multicast traffic loss.
NAE
CR_24268
Symptom: Network Analytics Engine (NAE) Agents report missing or inaccurate data.
Scenario: When the client and switch UTC times are mismatched, NAE reports missing or inaccurate data.
Workaround: Make sure the client and the switch translate to the same UTC time.
OSPF
CR_08491
Symptom/Scenario: OSPFv2 and OSPFv3 do not support detailed LSA show commands.
Workaround: Use the diag command, instead.
VRRP
CR_24910
Symptom: Unable to configure same IPv6 link local address as primary virtual IP address under different VRFs.
Scenario: Unique virtual link local addresses have to be configured for all VRRP IPv6 instances irrespective of
VRF.
Workaround: Do not use the same virtual link local address across different VRFs.
Feature caveats
Feature Description
sFlow and Mirroring sFlow and port mirroring are mutually exclusive per port. A port cannot
support both sFlow and mirroring at the same time.
IGMP Snooping and MCLAG IGMP Snooping and MCLAG are mutually exclusive within a VLAN.
MVRP and MCLAG MVRP is mutually exclusive with MCLAG.
MCLAG and STP (RPVST+ or MSTP) Spanning Tree (RPVST+ and MSTP) is mutually exclusive with
MCLAG.
RPVST+ and MSTP Spanning Tree can only run in MSTP or RPVST+ mode.
RPVST+ and MVRP RPVST+ is mutually exclusive with MVRP.
VRRP and Proxy ARP VRRP is mutually exclusive with Proxy ARP on the same interface.
IGMP/PIM on Loopback and GRE PIM and IGMP cannot be enabled on Loopback and GRE interfaces.
interfaces
Supportability Syslog server configuration is supported on the default VRF for access
over data ports.
Counters Layer 3 Route-only port counters are not enabled by default. Enabling
them will remove them from the counter resources shared with ACLs.
Table Continued
Upgrade information
Version 10.00.0010 uses ServiceOS GT.01.01.0005.
Prerequisites
The management port is connected and configured to use DHCP for obtaining the IP address. Both TFTP and
SFTP use the management port to download the image onto the switch.
Procedure
TFTP
Before using TFTP to transfer the software to the switch, make sure:
• A software version for the switch has been stored on a TFTP server accessible to the switch via management
port. (The software file is typically available from the Switch Networking website at http://www.hpe.com/
networking/support.)
• The switch is properly connected to your network via the management port and has already been configured
with a compatible IP address and subnet mask.
• The TFTP server is accessible to the switch via IP. Before you proceed, complete the following:
◦ Obtain the IP address of the TFTP server in which the software file has been stored.
◦ Determine the name of the software file stored in the TFTP server for the switch (for example, ArubaOS-
CX_8400X_10_00_0005.swi.)
SFTP
For some situations you may want to use a secure method to issue commands or copy files to the switch. By
opening a secure, encrypted SSH session and enabling IP SSH file transfer, you can then use a third-party
software application to take advantage of SFTP. SFTP provide a secure alternative to TFTP for transferring
information that may be sensitive (like switch configuration files) to and from the switch. Essentially, you are
creating a secure SSH tunnel as a way to transfer files with SFTP channels.
Before using SFTP to transfer the software to the switch, make sure:
• A software version for the switch has been stored on a computer accessible to the switch via management
port. (The software file is typically available from the Switch Networking website at http://www.hpe.com/
networking/support.)
• The switch is properly connected to your network via the management port and has already been configured
with a compatible IP address and subnet mask.
• The computer containing the software image is accessible to the switch via IP. Before you proceed, complete
the following:
◦ Obtain the IP address of the computer on which the software file has been stored.
◦ Determine the name of the software file stored on the computer for the switch (for example, ArubaOS-
CX_8400X_10_00_0005.swi.)
• Establish a secure encrypted tunnel between the switch and the computer containing the software update file
(for more information, see the Fundamentals Guide for your switch).
This is a one-time procedure. If you have already setup a secure tunnel, you can skip this step.
• Enable secure file transfer using the ssh server vrf <VRF-name> command (for more information, see
the Command-Line Interface Guide for your switch).
switch(config)# ssh server vrf mgmt
USB
Before using USB to transfer the software to the switch, make sure to:
switch(config)# usb
switch(config)# do usb mount
switch(config)# do show usb
Enabled: Yes
Mounted: Yes
1. Copy the software to the secondary flash on the switch using the copy <remote-URL> {primary |
secondary} [vrf <VRF-name>] command (for more information, see the Command-Line Interface Guide
for your switch).
• For TFTP:
Continue (y/n)? y
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 381M 100 381M 0 0 6755k 0 0:00:57 0:00:57 --:--:-- 6072k
100 381M 100 381M 0 0 6755k 0 0:00:57 0:00:57 --:--:-- 6755k
Continue (y/n)? y
[email protected]'s password:
Connected to 192.0.2.0.
sftp> get ArubaOS-CX_8400X_10_00_0005.swi ArubaOS-CX_8400X_10_00_0005.swi.dnld
Fetching /users/jdoe/ArubaOS-CX_8400X_10_00_0005.swi to ArubaOS-CX_8400X_10_00_0005.swi.dnld
/user/ArubaOS-CX_8400X_10_00_0005.swi 100% 382MB 95.4MB/s 00:04
• For USB:
Continue (y/n)? y
When the switch finishes downloading the software file, it displays this progress message:
----------------------------------------------------------------------------
ArubaOS-CX Primary Image
----------------------------------------------------------------------------
Version : XL.10.00.0001
----------------------------------------------------------------------------
ArubaOS-CX Secondary Image
----------------------------------------------------------------------------
Version : XL.10.00.0005
Size : 143 MB
Date : 2017-06-30 14:02:34 PDT
SHA-256 : 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
------------------------------------------------------
Management Module 1/5 (Active)
------------------------------------------------------
Active Image : Primary
Service OS Version : GT.01.01.0001
BIOS Version : GT-01-0013
------------------------------------------------------
Management Module 1/6 (Standby)
------------------------------------------------------
Active Image : Secondary
Service OS Version : GT.01.01.0001
BIOS Version : GT-01-0013
3. You must reboot the switch to implement the newly downloaded software image using the boot system
[primary | secondary | serviceos] command (for more information, see the Command-Line
Interface Guide for your switch).
A Security Bulletin is the first published notification of security vulnerabilities and is the only communication
vehicle for security vulnerabilities.
• Fixes for security vulnerabilities are not documented in manuals, release notes, or other forms of product
documentation.
• A Security Bulletin is released when all vulnerable products still in support life have publicly available images
that contain the fix for the security vulnerability.
Networking Websites
Hewlett Packard Enterprise Networking Information Library
www.hpe.com/networking/resourcefinder
Hewlett Packard Enterprise Networking Software
www.hpe.com/networking/software
Hewlett Packard Enterprise Networking website
www.hpe.com/info/networking
Hewlett Packard Enterprise My Networking website
www.hpe.com/networking/support
Hewlett Packard Enterprise My Networking Portal
www.hpe.com/networking/mynetworking
Hewlett Packard Enterprise Networking Warranty
www.hpe.com/networking/warranty
General websites
Hewlett Packard Enterprise Information Library
www.hpe.com/info/EIL
For additional websites, see Support and other resources.
Chapter 3 Websites 31
Chapter 4
Support and other resources
• To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:
http://www.hpe.com/support/hpesc
Information to collect
Accessing updates
• Some software products provide a mechanism for accessing software updates through the product interface.
Review your product documentation to identify the recommended software update method.
• To download product updates:
Hewlett Packard Enterprise Support Center
www.hpe.com/support/hpesc
Hewlett Packard Enterprise Support Center: Software downloads
www.hpe.com/support/downloads
Software Depot
www.hpe.com/support/softwaredepot
• To subscribe to eNewsletters and alerts:
www.hpe.com/support/e-updates
• To view and update your entitlements, and to link your contracts and warranties with your profile, go to the
Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page:
Access to some updates might require product entitlement when accessed through the Hewlett
Packard Enterprise Support Center. You must have an HPE Passport set up with relevant
entitlements.
Remote support
Remote support is available with supported devices as part of your warranty or contractual support agreement. It
provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett
Packard Enterprise, which will initiate a fast and accurate resolution based on your product's service level.
Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
If your product includes additional remote support details, use search to locate that information.
Warranty information
To view the warranty for your product or to view the Safety and Compliance Information for Server, Storage,
Power, Networking, and Rack Products reference document, go to the Enterprise Safety and Compliance website:
www.hpe.com/support/Safety-Compliance-EnterpriseProducts
Regulatory information
To view the regulatory information for your product, view the Safety and Compliance Information for Server,
Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise Support Center:
www.hpe.com/support/Safety-Compliance-EnterpriseProducts
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve
the documentation, send any errors, suggestions, or comments to Documentation Feedback
([email protected]). 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.