HPE H55VWA3#ZTP SN8700B 48-Port Blade Zero Touch Provisioning Support
Overview
The HPE H55VWA3#ZTP delivers Zero Touch Provisioning (ZTP) support for the HPE SN8700B 64GB 48-port blade, enabling automated network device bring-up over Ethernet without manual CLI intervention at each node. In large-scale data center or campus deployments where provisioning dozens of blade switches by hand would create unacceptable commissioning overhead, ZTP automates the bootstrap sequence — the switch contacts a DHCP server on first boot, receives pointers to its configuration and firmware image files, and self-configures with no on-site technician required.
Compatibility
Designed specifically for the HPE SN8700B 64GB platform, 48-port blade variant. ZTP provisioning operates over Ethernet and relies on DHCP Option 43 and Option 17 suboption delivery. The following suboptions are supported: suboption 144 carries the configuration file name; suboption 145 carries the firmware image file name; suboption 146 specifies the FQDN or IPv4 address of the Aruba Central on-premise server; suboption 148 specifies the FQDN, IPv4, or IPv6 address of the HTTP proxy. Option 17 suboptions mirror this structure with suboption 144 for the configuration file and suboption 145 for the firmware image. Verify your DHCP server supports vendor-specific option encoding (Option 43 or Option 17) before deployment — not all DHCP implementations expose suboption-level configuration without additional setup.
Installation Notes
ZTP requires a reachable DHCP server on the same Layer 2 segment as the blade's management interface, or a DHCP relay configured to forward requests to the provisioning server. The FQDN entries in suboptions 146 and 148 must be DNS-resolvable from the blade's network context at boot time. HTTP proxy configuration via suboption 148 supports both IPv4 and IPv6 addressing, allowing provisioning traffic to route through existing proxy infrastructure. Confirm Aruba Central on-premise server reachability and that the firmware image and configuration files are staged at the expected paths before the blade is powered on — ZTP has no interactive fallback if the file references are unreachable.
