SD-WAN

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

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.

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

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