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
ArubaOS-CX 10.01 Release Notes
Description
This release note covers software versions for the ArubaOS-CX 10.01 branch of the software.
If you run the
show version
command on the 8400, the version number will display XL.10.01.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.01.0001 was the initial build of major version 10.01 software.
Product series supported by this software:
Aruba 8400 Switch Series
Important information
To avoid damage to your equipment, do not interrupt power to the switch during a software update.
Version 10.01 includes new ServiceOS GT.01.02.0003 and updates for a number of components for the management modules, fabric modules, and line modules.
The upgrade process to this version from version 10.00.0018 and earlier may take ~30 minutes to complete, depending on system configuration. During this upgrade, the management, fabric, and line modules will be rebooted several times.
If you are upgrading from version 10.00 and the switch is configured with MCLAG, VSX reconfiguration is required after the upgrade. Network downtime is required for this upgrade. For more information on upgrading from MCLAG to VSX, see the ArubaOS-CX Virtual Switching Extension (VSX) Guide.
If you are upgrading from version 10.00.0018 or earlier, read through the entire upgrade procedure before proceeding.
If you are upgrading from version 10.00.00xx, upon the first time booting to XL.10.01.0011 a new version of ServiceOS GT.01.02.003 will be updated, followed by updates to the management modules. During management module component updates several reboot sequences will take place. At the switch console port an output similar to the following will be displayed as various components are being updated:
8400X# boot system Checking for updates needed to programmable devices... Done checking for updates. 43 device(s) need to be updated during the boot process. The estimated update time is 23 minute(s). There may be multiple reboots during the update process. This will reboot the entire switch and render it unavailable until the process is complete. Continue (y/n)? y The system is going down for reboot. reboot: Restarting system Press Esc for boot options ServiceOS Information: Version: GT.01.01.0003 Build Date: 2017-09-29 10:29:03 PDT Build ID: ServiceOS:GT.01.01.0003:961dc6c2c4ee:201709291029 SHA: 961dc6c2c4ee28cc9587fcf44e40c46c26b8349b Boot Profiles: 0. Service OS Console 1. Primary Software Image [XL.10.01.0011] 2. Secondary Software Image [XL.10.00.0018] Select profile(primary): ISP configuration: Auto updates : enabled Version comparisons : normal (upgrade only) [DEFAULT] Unsafe updates : not allowed (DEFAULT) MODULE 'mc' DEVICE 'svos_primary' : Current version : 'GT.01.01.0005' Write-protected : NO Packaged version : 'GT.01.02.0003' Package name : 'svos' Image filename : 'GT_01_02_0003.svos' Image timestamp : 'Fri May 11 22:37:39 2018' Image size : 25077231 Version upgrade needed Starting update… . . . Update successful
The 8400 will continue to reboot and report what is remaining to update and the update time.
After all the needed updates have completed the switch console will arrive to login prompt.
Booting primary software image... Verifying Image... Image Info: Name: ArubaOS-CX Version: XL.10.01.0011 Build Id: ArubaOS-CX:XL.10.01.0011:14e95a5aa927:201806271551 Build Date: 2018-06-27 09:16:50 PDT Extracting Image... Loading Image... Done. kexec_core: Starting new kernel 8400X login:
When all updates are completed, the line modules status will display "Ready" in the output of the
show module
command.8400X# show module Management Modules ================== Product Serial Name Number Description Number Status ---- ------- -------------------------------------- ---------- ---------------- 1/5 JL368A 8400 Mgmt Mod SG7BK27032 Active (local) 1/6 JL368A 8400 Mgmt Mod SG70K2700Q Standby Line Modules ============ Product Serial Name Number Description Number Status ---- ------- -------------------------------------- ---------- ---------------- 1/1 JL363A 8400X 32P 10G SFP/SFP+ Msec Mod SG7AK2201C Ready 1/2 JL363A 8400X 32P 10G SFP/SFP+ Msec Mod SG70K22051 Ready
IMPORTANT:HPE does not recommend to perform any configuration changes until all upgrades completed.
Version history
All released versions are fully supported by Hewlett Packard Enterprise, unless noted in the table.
Products supported
Compatibility/interoperability
The switch web agent supports the following web browsers:
Browser | Minimum supported versions |
---|---|
Edge (Windows) | 38 |
Chrome (Ubuntu) | 54 (desktop) 56 (mobile) |
Firefox (Ubuntu) | 52 |
Safari (MacOS, IOS Only) | 10 |
Internet Explorer is not supported.
The following table provides information on compatibility of the switches found in this release note with network management software:
Management software | Supported version(s) |
---|---|
Airwave | |
Network Automation | 10.10, 10.11, 10.20, 10.21, 10.30, 10.40 |
Network Node Manager i | 10.10, 10.20, 10.21, 10.30, 10.40 |
IMC |
For more information, see the respective software manuals.
Minimum supported software versions
If your switch or module is not listed in the below table, it runs on all versions of the 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.01.0011
No enhancements were included in version 10.01.0011.
Version 10.01.0001
Aruba Virtual Switching Extension
Aruba Virtual Switching Extension (VSX) is a Virtualized Core and Aggregation solution designed to meet the high availability, virtualization, and simplicity needs unique to the core of the network. It is designed for high availability. Aruba VSX enables a distributed and redundant architecture that is highly available during upgrades inherently by architecture design. Operationally, Aruba VSX includes features to ensure enhanced and robust configuration and consistency checking and capabilities to make upgrades minimally disruptive.
BFD
BGP
The following enhancements were added:
- Autonomous-System-Wide (4-Byte) Unique BGP Identifier for BGP-4 (RFC 6286)
- TTL Security
- Next-Hop Address tracking
- Textual Representation of Autonomous System (AS) (RFC 5396)
- Regex for IP Community list
- Multiple AS Path enable
- Routemap: 4-byte AS Path
- Routemap: Allow set for multiple Individual Community Number
- Enhanced Route Refresh Capability for BGP-4 (RFC 7313)
Autonomous System (AS) Reservation for Private Use (RFC 6696)
ICMP
Inter VRF route leaking
LAGs
Added support for MTU on LAG interfaces. When MTU is set for a LAG interface, the configured value is propagated to all port members of the LAG interface. If a member is removed from a LAG interface, the MTU value is reverted to the default for the respective member. An interface cannot add a member to a LAG when the LAG MTU value is higher than the maximum MTU value allowed for the physical interface.
Network Analytics Engine
OSPF
The following enhancements were added:
IPsec authentication support
Route map support (v2 and v3)
Reference bandwidth updated for 100G speeds (v2 and v3)
RFC 4222 support to enable more reliable OSPF processing in high load scenarios (v2 and v3)
Area range aggregation Type-3/Type-7 address ranges (v3)
Virtual links (v3)
Configuration of virtual link parameters hello-interval, dead-interval, retransmit-interval, transit-delay, etc. (v3)
NSSA (v3)
PIM-SM
SPAN to a LAG
Static ARP and Static MAC
TACACS Accounting
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.01.0011
DHCP Relay
CR_37060
Symptom: In certain conditions, clients are unable to obtain a DHCP IP address.
Scenario: When the switch is configured for DHCP relay and the DHCP server is sending DHCP options with lengths greater than 127, the DHCP relay agent fails to correctly relay the DHCP packet to the clients and may trigger high CPU utilization.
Workaround: Reduce the length of DHCP options sent by the DHCP server.
L3 Addressing
CR_23936
Line module
CR_36536
Symptom: In certain conditions, the switch line module fails to initialize.
Scenario: In a fully loaded switch, the 40G line module may fail to initialize during the switch boot up and the switch reports an error message similar to
router-a hpe-cardd[1808]: Event|Unknown Event Name MODULE_ASIC_DEINIT_TIMEOUT
.
Multicast
CR_23498
CR_37731
PIM
CR_37322
CR_37519
SNMP
CR_36117
Symptom: The switch fails SNMPv3 user authentication.
Scenario: After updating the SNMPv3 user password in the switch configuration, the switch fails to authenticate the SNMPv3 user with the new configured password.
Workaround: Remove the SNMPv3 user from switch configuration and re-add with the new password,
CR_37471
Version 10.01.0001
ARP
CR_25306
Config
CR_36595
Symptom: The switch fails to download ceratin configurations from a remote server.
Scenario: When a switch configuration file includes user-defined strings, such as (but not limited to) route-map names and banner strings, with special character #, the switch may fail to download the configuration file in a CLI format to the switch running-config from a remote server using SCP/SFTP.
Workaround: Use JSON type for switch configuration backup and restore from a remote server or use configuration checkpoint to save and restore the switch configuration when special character # is needed.
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.
NAE
CR_24268
SNMPv3
CR_36512
Symptom: The switch fails authentication during SNMPv3 discovery.
Scenario: After changing the authentication and/or privacy protocol of an existing SNMPv3 user, the SNMPv3 user authentication fails. For example:
Change from:
snmpv3 user username auth md5 auth-pass passpass priv des priv-pass passpass
Change to:
snmpv3 user username auth sha auth-pass passpass priv aes priv-pass passpass
Workaround: Remove the SNMPv3 user and re-add it with the new authentication and/or privacy protocol using the
no
form of the command. For example:
no snmpv3 user username auth md5 auth-pass passpass priv aes priv-pass passpass
snmpv3 user username auth sha auth-pass passpass priv aes priv-pass passpass
Issues and workarounds
The following are known open issues with this branch of the software.
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.
ARP
CR_25334
Symptom: Total number of neighbors is greater than the configured cache limit.
Scenario: Neighbor addition to the ARP table is not guaranteed when the amount of total neighbors is greater than the configured cache limit.
Workaround: Limit the total number of neighbors to be within the configured cache limit of 128K.
CLI
CR_34128
Symptom: Some CLI commands do not execute properly.
Scenario: After interrupting the output of a CLI command before its completion, using CTRL+C, some subsequent command executions may not function properly.
Workaround: Use CTRL+C to again terminate the output of the CLI command or close out all current sessions to the switch and re-open a new session.
Config
CR_37884
Symptom: Copying a configuration file in CLI format from server to switch startup-config fails with an error message.
Scenario: When copying a configuration file from server to switch startup-config in CLI format fails with the error message
DryRun: writeVtyCliCmd timeout waiting on writeJSON regeneration failed - try after sometime
. Copying the same configuration into the running-config works.
Workaround: On a switch without any configuration, the workaround is to copy the config file into running-config. If the switch has a configuration that should be replaced, then user must delete the existing configuration, reboot, then copy the config into running-config. For example,
copy tftp://<server-ip>/<file-path> running-config vrf
<vrf-name>
.
Jumbo Frames
CR_25546
L3 Addressing
CR_12008
Multicast
CR_37873
Symptom: Multicast routes are not learned when using an interface as a default route. For example: ip route 0.0.0.0/0 1/2/16.
Scenario: Multicast will not do RPF neighbor calculation, since it is not able to resolve the next hop IP from just an outgoing interface.
Workaround: Use only IP-based static routes to configure the next hop routes for Multicast, not interfaces. For example: ip route 0.0.0.0/0 30.1.1.1.
OSPF
CR_08491
CR_36228
Symptom: The switch does not support the double quote (") character in the authentication key string.
Scenario: When configuring IPSec authentication for the OSPFv3 area, the switch does not accept an authentication key string containing the double quote (") character. For example:
area 100 authentication ipsec spi 12341 sha1 plaintext @%^&*(__+={]:;-".\/A
Invalid input: @%^&*(__+={]:;-".\/A
Workaround: Use a key string without the double quote (") character when enabling IPSec authentication key for the OSPFv3 area.
CR_37954
Symptom: OSPFv3 neighbor ship is broken after ISL flap on VSX-Secondary.
Scenario: OSPFv3 neighbor ship is broken after ISL Flap on VSX-Secondary on Active Forwarding. OSPFv3 not forming between VSX-Secondary and router after ISL flap.
Workaround: Disable and re-enable the SVI attached to the VSX Interfaces (Active-forwarded SVIs) using the
shutdown
and
no shutdown
commands.
Transceivers
CR_36115
Symptom: JL563A 10Gb transceivers fail in the
waiting for link
state.
Scenario: After hotswapping from a 1Gb transceiver to the JL536A 10Gb SFP+ transceiver, the new transceiver fails to obtain a link.
Workaround: Disable the port using the
shutdown
command and then re-enable it with the
no shutdown
command.
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.
VSX
CR_37952
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. |
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 interfaces | PIM and IGMP cannot be enabled on Loopback and GRE interfaces. |
Counters | Layer 3 Route-only port counters are not enabled by default. Enabling them will remove them from the counter resources shared with ACLs. |
Counters | Counters are shared between ACL and Layer 3 ports. The Max number of ACL entries with count action plus Layer 3 counters is: JL363A=24K, JL365A=24K, JL366A=8K. Enabling counters on a Layer 3 port consumes 6 ACL counter entries. |
Counters | Classifier Counters: Max number Classifier entries with count action: JL363A=12.8K, JL365A=12.8K, JL366A=6.4K. |
UDLD | For a UDLD-enabled interface to not lose traffic during a failover operation, the result of multiplying 'interval' and 'retries' should be at least 8 seconds. The default values are 7000 ms (interval) x 4 (retries) = 28 seconds. |
Network Analytics Engine (NAE) | Agents monitoring a resource that has column type enum with a list of strings (as opposed to a single string enum) is not supported. |
Network Analytics Engine (NAE) | After management module failover, up to 5 minutes of alert history could be lost. |
Network Analytics Engine (NAE) | The following tables are not supported for NAE scripts: OSPF_Route, OSPF_LSA, OSPF_Neighbor, BGP_Route. |
Network Analytics Engine (NAE) | Network Analytics Engine (NAE) agents execute Command Line Interface (CLI) actions as 'admin' user, so they have permission to run any command by default. However, when the authentication, authorization and accounting (AAA) feature is enabled, the same restrictions applied to 'admin' will also apply to NAE agents. Keep that in mind when configuring the AAA service, e.g. TACACS+, and make sure to give admin user permission to run all commands needed by enabled agents. Otherwise, some CLI commands may be denied and their outputs won't be available. Actions other than CLI won't be affected and will execute normally. Also, NAE agents won't authenticate, thus the AAA service configuration must not block authorization for unauthenticated 'admin' user. ClearPass doesn't support such configuration, so it cannot be used as a TACACS+ server. |
Classifiers | IPv4 egress ACLs can be applied only to route-only ports. |
Classifiers | Classifier policies, IPv6 and MAC ACLs are not supported on egress. |
Classifiers | DSCP remarking is performed only on routed packets. |
Classifiers | For security ACLs, HPE strongly encourages modifications be done as a two step process: Bring down the port and then modify. |
Classifiers | Policies containing both MAC and IPv6 classes are not allowed. |
REST | REST supports the 'admin' and 'operator' roles but does not work with TACACS+ command authorization. |
REST | With the exception of ACLs and VLANs, REST APIs using POST/PUT/DELETE are not validated before performing the function. Therefore, to avoid unintended results or side effects, HPE recommends testing the API write action first. |
VSX | VSX active-forwarding only works when the L3 interface is IPv4. Enabling it on an interface that has dual-stack or IPv6 may result in traffic losses. |
Upgrade information
Do not interrupt power to the switch during this important update.
If you are upgrading from version 10.00 and the switch is configured with MCLAG, VSX reconfiguration is required after the upgrade. Network downtime is required for this upgrade. For more information on upgrading from MCLAG to VSX, see the ArubaOS-CX Virtual Switching Extension (VSX) Guide.
File transfer methods
The switches support several methods for transferring files to and from a physically connected device or via the network, including TFTP, SFTP, and USB. This section explains how to download and run new switch software.
File transfer setup
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.
If your TFTP server is a UNIX workstation, ensure that the case (upper or lower) that you specify for the filename is the same case as the characters in the software filenames on the server.
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.
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).
NOTE: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:
Store a software version on a USB flash drive.
Determine the name of the software file stored on the USB flash drive.
Enable USB on the switch:
switch(config)# usb switch(config)# do usb mount switch(config)# do show usb Enabled: Yes Mounted: Yes
Copying the software and rebooting the switch
Hewlett Packard Enterprise security policy
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.
Finding Security Bulletins
- Go to the HPE Support Center - Hewlett Packard Enterprise at www.hpe.com/support/hpesc.
- Enter your product name or number and click Go.
- Select your product from the list of results.
- Click the Top issues & solutions tab.
- Click the Advisories, bulletins & notices link.
Security Bulletin subscription service
You can sign up at http://www.hpe.com/support/Subscriber_Choice to initiate a subscription to receive future Hewlett Packard Enterprise Security Bulletin alerts via email.
Websites
Networking Websites
- Hewlett Packard Enterprise Networking Information Library
- Hewlett Packard Enterprise Networking Software
- Hewlett Packard Enterprise Networking website
- Hewlett Packard Enterprise My Networking website
- Hewlett Packard Enterprise My Networking Portal
- Hewlett Packard Enterprise Networking Warranty
General websites
- Hewlett Packard Enterprise Information Library
For additional websites, see Support and other resources.
Support and other resources
Accessing Hewlett Packard Enterprise Support
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website:
Information to collect
Technical support registration number (if applicable)
Product name, model or version, and serial number
Operating system name and version
Firmware version
Error messages
Product-specific reports and logs
Add-on products or components
Third-party products or components
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:
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.
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
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.
Remote support and Proactive Care information
- HPE Get Connected
- www.hpe.com/services/getconnected
- HPE Proactive Care services
- www.hpe.com/services/proactivecare
- HPE Proactive Care service: Supported products list
- www.hpe.com/services/proactivecaresupportedproducts
- HPE Proactive Care advanced service: Supported products list
- www.hpe.com/services/proactivecareadvancedsupportedproducts
Proactive Care customer information
- Proactive Care central
- www.hpe.com/services/proactivecarecentral
- Proactive Care service activation
- www.hpe.com/services/proactivecarecentralgetstarted
Warranty information
To view the warranty information for your product, see the links provided below:
- HPE ProLiant and IA-32 Servers and Options
- www.hpe.com/support/ProLiantServers-Warranties
- HPE Enterprise and Cloudline Servers
- www.hpe.com/support/EnterpriseServers-Warranties
- HPE Storage Products
- www.hpe.com/support/Storage-Warranties
- HPE Networking Products
- www.hpe.com/support/Networking-Warranties
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:
Additional regulatory information
Hewlett Packard Enterprise is committed to providing our customers with information about the chemical substances in our products as needed to comply with legal requirements such as REACH (Regulation EC No 1907/2006 of the European Parliament and the Council). A chemical information report for this product can be found at:
For Hewlett Packard Enterprise product environmental and safety information and compliance data, including RoHS and REACH, see:
For Hewlett Packard Enterprise environmental information, including company programs, product recycling, and energy efficiency, see:
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 (docsfeedback@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.