We have a similar project with around 100 x A9004-LTE.
We ''Pre-stage'' them from our office before shipping to customer.
Connecting to local lan with DHCP (factory default v8.7) then upgrade then in central and add config as needed.
For your case above, are you sure they are added to your HPE Greenlake devices with Serial Number and Mac and licenses to your Greenlake prior to connecting then?
Also seems to me from logs to be a resolving issue towards arubanetworks.com
Original Message:
Sent: Jun 12, 2024 07:24 AM
From: scottdoorey
Subject: 9004-LTE - static-activate config not working - no traffic flow
unfortunately it seems to be the case recently, tac have outright refused support if its not an existing deployment, directing me to my local SE or partner ( i am the partner!)
its crazy but true.
I've got a 200+ site deployment where the boxes are shipping with 8.7 code, if its worthy of shipping it should be supported!
in the end i used full setup mode to get it into central and then upgrade to 10.5 and got where i needed to be but having to do this on 200+ sites is going to be painful.
can't do ZTP as customer ISP does not support DHCP. what is this 1990?
Original Message:
Sent: Jun 12, 2024 07:03 AM
From: Herman Robers
Subject: 9004-LTE - static-activate config not working - no traffic flow
I could think that TAC is not supporting ArubaOS 8.7 as that is end-of-support, but even if you have a new deployment and things don't work according the documentation, TAC should assist you. They may not go to the same escalation level compared to a 'network down' from something that worked.
If you can upgrade the controller to 8.10 or other supported version, you can see if the same happens. Another suggestion would be to temporarily setup a DHCP server that announces the provider's router as default gateway, and working DNS server. Probably once firmware is updated and provisioning has happened, all is probably good.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jun 11, 2024 07:03 PM
From: scottdoorey
Subject: 9004-LTE - static-activate config not working - no traffic flow
Hey Airheads,
I'm trying to deploy a 9004-LTE as a branch gateway. Its running 8.7.0.0-2.3.0.8 out of the box and my client doesn't have DHCP based internet services so i have to use the static-activate method.
The problem i'm facing is that when i do the static-activate config and define the uplink VLAN / interface and IP addresses, the device doesn't even try and connect to activate or central and actually reports unable to resolve the FQDN for device.arubanetworks.com.
I've plugged directly in and confirmed that the ISP service is working and DNS resolving. I also connected uplink to my laptop and ran a PCAP to confirm that no data was being sent. I could ping the gateway IP but no data coming from it for DNS or next hop.
I reconfigure to use E 0/0/1 and still the same.
When i used the full setup method and applied the same settings the device came online.
I'm suspecting this is a bug but with TAC now rejecting support on cases for new deployments, i'm not able to seek help with this through TAC.
Surely i ca'n tbe the first person to run into this issue?
Here is my console output
Auto-provisioning is in progress. It requires DHCP and Activate servers
Choose one of the following options to override or debug auto-provisioning...
'enable-debug' : Enable auto-provisioning debug logs
'disable-debug' : Disable auto-provisioning debug logs
'full-setup' : Start full setup dialog. Provides full customization
'static-activate' : Provides customization for static or PPPOE ip assignment. Uses activate for master information
Enter Option (partial string is acceptable): Jun 10 18:48:08 LOG: Enabled logging
static-activate
Enter Controller VLAN ID [1]:
Enter Uplink port [GE 0/0/0]:
Enter Uplink port mode (access|trunk) [access]:
Enter Uplink Vlan IP assignment method (static|pppoe) [static]:
Enter Uplink Vlan Static IP address [192.168.1.1]: X.Y.Z.57
Enter Uplink Vlan Static IP netmask [255.255.255.0]: 255.255.255.0
Enter IP default gateway [none]: X.Y.Z.56
Enter DNS IP address [none]: 1.1.1.1
Do you wish to configure IPV6 address on vlan (yes|no) [yes]: no
Do you want to disable spanning tree (yes|no)? [no]:
Do you want to configure dynamic port-channel (yes|no) [no]:
Current choices are:
Controller VLAN id: 1
Uplink port: GE 0/0/0
Uplink port mode: access
Uplink Vlan IP assignment method: static
Uplink Vlan static IP Address: X.Y.Z.57
Uplink Vlan static IP net-mask: 255.255.255.0
Uplink Vlan IP default gateway: X.Y.Z.56
Domain Name Server to resolve FQDN: 1.1.1.1
Option to configure VLAN interface IPV6 address: no
Spanning-tree is disabled: no
Do you wish to accept the changes (yes|no)yes
Auto-provisioning is in progress. It requires DHCP and Activate servers
Choose one of the following options to override or debug auto-provisioning...
'enable-debug' : Enable auto-provisioning debug logs
'disable-debug' : Disable auto-provisioning debug logs
'full-setup' : Start full setup dialog. Provides full customization
'static-activate' : Provides customization for static or PPPOE ip assignment. Uses activate for master information
Enter Option (partial string is acceptable): Jun 10 18:49:29 LOG: Received manual override
Jun 10 18:49:29 LOG: Stopping Auto-Provisioning since Static-Acitvate Mode is chosen.
Jun 10 18:49:29 LOG: Manually provisioning removing access vlan to stop ZTP...
Jun 10 18:49:29 LOG: Executing cmd (interface gigabitethernet 0/0/2 no switchport access vlan)
Jun 10 18:49:29 LOG: Done (interface gigabitethernet 0/0/2 no switchport access vlan)
Jun 10 18:49:29 LOG: Manually provisioning removing access vlan to stop ZTP...
Jun 10 18:49:29 LOG: Executing cmd (interface gigabitethernet 0/0/3 no switchport access vlan)
Jun 10 18:49:29 LOG: Done (interface gigabitethernet 0/0/3 no switchport access vlan)
Jun 10 18:49:29 LOG: Manually provisioning trunk port...
Jun 10 18:49:29 LOG: Executing cmd (interface gigabitethernet 0/0/0 switchport mode access)
Jun 10 18:49:29 LOG: Done (interface gigabitethernet 0/0/0 switchport mode access)
Jun 10 18:49:29 LOG: Manually provisioning access vlan...
Jun 10 18:49:29 LOG: Executing cmd (interface gigabitethernet 0/0/0 switchport access vlan 1)
Jun 10 18:49:29 LOG: Done (interface gigabitethernet 0/0/0 switchport access vlan 1)
Jun 10 18:49:29 LOG: Manually provisioning IP...
Jun 10 18:49:29 LOG: Executing cmd (interface vlan 1 ip address X.Y.Z.57 255.255.255.0)
Jun 10 18:49:29 LOG: Done (interface vlan 1 ip address X.Y.Z.57 255.255.255.0)
Jun 10 18:49:29 LOG: Manually provisioning static Gateway...
Jun 10 18:49:29 LOG: Executing cmd (ip default-gateway X.Y.Z.56)
Jun 10 18:49:29 LOG: Done (ip default-gateway X.Y.Z.56)
Jun 10 18:49:29 LOG: Manually provisioning static nameserver...
Jun 10 18:49:29 LOG: Executing cmd (ip name-server 1.1.1.1)
Jun 10 18:49:29 LOG: Done (ip name-server 1.1.1.1)
Jun 10 18:49:44 LOG: Starting Activate communication
Jun 10 18:49:44 LOG: Sending provisioning parameters request to Activate
Jun 10 18:49:44 LOG: Posting message to Activate
Jun 10 18:49:44 LOG: Executing CURL Command /usr/sbin/curl https://device.arubanetworks.com/provision --cacert /flash/trustedCA/ca-bundle.crt -X POST -H Expect: --trace-ascii /var/log/oslog/activate/trace1.txt --retry 5 --max-time 20 -H "Connection: Keep-Alive" -H "X-Type: provision-update" -H "Content-Length: 0" -H "X-Mode: CONTROLLER" -H "X-Current-Version: 8.7.0.0-2.3.0.8_84688" -H "X-Ap-Info: *SERIAL*, *MAC*, Aruba9004-LTE" -D /var/log/oslog/activate/act_resp
Jun 10 18:49:44 LOG: Provisioning parameters request sent to Activate
Warning: Transient problem: timeout Will retry in 1 seconds. 5 retries left.
Warning: Transient problem: timeout Will retry in 2 seconds. 4 retries left.
Warning: Transient problem: timeout Will retry in 4 seconds. 3 retries left.
Warning: Transient problem: timeout Will retry in 8 seconds. 2 retries left.
Warning: Transient problem: timeout Will retry in 16 seconds. 1 retries left.
curl: (6) Could not resolve host: device.arubanetworks.com
Jun 10 18:50:15 LOG: Activate handler invoked for client 7928
Jun 10 18:50:15 ERR: Activate client failed with status 1536
Jun 10 18:50:15 ERR: Terminating Activate connection due to failure
Jun 10 18:50:15 LOG: Stopping Activate communication
Jun 10 18:50:15 LOG: Destroying Activate context
Jun 10 18:50:15 LOG: Calling response handler
Provisioning Parameters not received from Activate, will retry after 30 seconds
Jun 10 18:50:15 ERR: Activate failed, will retry after 30 seconds
Jun 10 18:50:15 LOG: Acitvate retry count is 1
Jun 10 18:50:45 LOG: Retrying Activate device.arubanetworks.com
Jun 10 18:50:45 LOG: Starting Activate communication
Jun 10 18:50:45 LOG: Sending provisioning parameters request to Activate
Jun 10 18:50:45 LOG: Posting message to Activate
Jun 10 18:50:45 LOG: Executing CURL Command /usr/sbin/curl https://device.arubanetworks.com/provision --cacert /flash/trustedCA/ca-bundle.crt -X POST -H Expect: --trace-ascii /var/log/oslog/activate/trace1.txt --retry 5 --max-time 20 -H "Connection: Keep-Alive" -H "X-Type: provision-update" -H "Content-Length: 0" -H "X-Mode: CONTROLLER" -H "X-Current-Version: 8.7.0.0-2.3.0.8_84688" -H "X-Ap-Info: *SERIAL*, *MAC*, Aruba9004-LTE" -D /var/log/oslog/activate/act_resp
Jun 10 18:50:45 LOG: Provisioning parameters request sent to Activate
Warning: Transient problem: timeout Will retry in 1 seconds. 5 retries left.
Warning: Transient problem: timeout Will retry in 2 seconds. 4 retries left.
Warning: Transient problem: timeout Will retry in 4 seconds. 3 retries left.
Warning: Transient problem: timeout Will retry in 8 seconds. 2 retries left.
Warning: Transient problem: timeout Will retry in 16 seconds. 1 retries left.
curl: (6) Could not resolve host: device.arubanetworks.com
Jun 10 18:51:16 LOG: Activate handler invoked for client 8103
Jun 10 18:51:16 ERR: Activate client failed with status 1536
Jun 10 18:51:16 ERR: Terminating Activate connection due to failure
Jun 10 18:51:16 LOG: Stopping Activate communication
Jun 10 18:51:16 LOG: Destroying Activate context
Jun 10 18:51:16 LOG: Calling response handler
Provisioning Parameters not received from Activate, will retry after 30 seconds
Jun 10 18:51:16 ERR: Activate failed, will retry after 30 seconds
Jun 10 18:51:16 LOG: Acitvate retry count is 2
Jun 10 18:51:46 LOG: Retrying Activate device.arubanetworks.com
Jun 10 18:51:46 LOG: Starting Activate communication
Jun 10 18:51:46 LOG: Sending provisioning parameters request to Activate
Jun 10 18:51:46 LOG: Posting message to Activate
Jun 10 18:51:46 LOG: Executing CURL Command /usr/sbin/curl https://device.arubanetworks.com/provision --cacert /flash/trustedCA/ca-bundle.crt -X POST -H Expect: --trace-ascii /var/log/oslog/activate/trace1.txt --retry 5 --max-time 20 -H "Connection: Keep-Alive" -H "X-Type: provision-update" -H "Content-Length: 0" -H "X-Mode: CONTROLLER" -H "X-Current-Version: 8.7.0.0-2.3.0.8_84688" -H "X-Ap-Info: *SERIAL*, *MAC*, Aruba9004-LTE" -D /var/log/oslog/activate/act_resp
Jun 10 18:51:46 LOG: Provisioning parameters request sent to Activate
Warning: Transient problem: timeout Will retry in 1 seconds. 5 retries left.
Warning: Transient problem: timeout Will retry in 2 seconds. 4 retries left.
Warning: Transient problem: timeout Will retry in 4 seconds. 3 retries left.
Warning: Transient problem: timeout Will retry in 8 seconds. 2 retries left.
Warning: Transient problem: timeout Will retry in 16 seconds. 1 retries left.
curl: (6) Could not resolve host: device.arubanetworks.com
Jun 10 18:52:17 LOG: Activate handler invoked for client 8274
Jun 10 18:52:17 ERR: Activate client failed with status 1536
Jun 10 18:52:17 ERR: Terminating Activate connection due to failure
Jun 10 18:52:17 LOG: Stopping Activate communication
Jun 10 18:52:17 LOG: Destroying Activate context
Jun 10 18:52:17 LOG: Calling response handler
Provisioning Parameters not received from Activate, will retry after 30 seconds
Jun 10 18:52:17 ERR: Activate failed, will retry after 30 seconds
Jun 10 18:52:17 LOG: Acitvate retry count is 3