Cloud Managed Networks

 View Only

  • 1.  Virtual Gateway 10.3.1.1 in Azure deployment

    Posted Oct 18, 2022 10:23 AM
    Hi,

    I'm trying to install a VGW instance in Azure with the ArubaOS_VGW_10.3.1.1_84780.vhd image from ASP.
    In one of the steps described in the manual, I create the virtual gateway in Aruba Central and download the "userdata" needed to create the VM in Azure.
    The userdata looks like this:
     
    central_url:device-eucentral3.central.arubanetworks.com
serial_no:VG2210176301
username:"VG2210176301,02:1A:1E:3B:3C:6F,MC-VA,VGW"
password:<somelongpassword>
mac_address:02:1A:1E:3B:3C:6F
part_number:MC-VA
mode:VGW
interfaces:eth0, eth1, eth2, eth3
group_name:Azure Cloud
bandwidth_sku:VGW-500MB
group_id:2
eth3:LAN
eth2:VPN
eth1:INET
eth0:LAN

    The VGW is created with the userdata and boots (I can follow the boot via the serial console in Azure), but doesn't seem to receive its config from Central.
    I then configure it manually using the "full-configure" option and when doing a show inventory I get the following:

     
    (VPNC-Demo) *[mynode] #show inventory

Mgmt Port HW MAC Addr           : 60:45:BD:8F:2F:51
HW MAC Addr                     : 00:0D:3A:AE:29:66
System Serial#                  : 
Activate license                : Not Applicable
Active device type              : VGW-MEDIUM
(VPNC-Demo) *[mynode] #

    As you can see, the MAC address is incorrect and the System Serial# has not been filled in at all.
    Same for the Aruba Central part:

     
    (VPNC-Demo) *[mynode] # show aruba-central details

Aruba Central
-------------
Parameter                       Value
---------                       -----
Aruba Central IP/URL            Unknown
Connection Status               DOWN
Time of last disconnect         N/A
SmartAmon MON Bootstrap Status  Init
Number of times WS connected    0
Time of last connect            N/A
(VPNC-Demo) *[mynode] #

    The Aruba Central URL from the userdata is not in there.
    On top of that, the VGW only has 3 GigabitEthernet interfaces, although the manual and userdata configures four of them.

    Can someone help me? Is this a change in Azure that is not yet in the Aruba documentation or is this to do with the change from 8.x to 10.x AOS versions?

    Thanks for any help,




    ------------------------------
    Steven Demets
    Solutions Architect
    Quant ICT
    https://quant.be
    ------------------------------


  • 2.  RE: Virtual Gateway 10.3.1.1 in Azure deployment

    Posted Oct 25, 2022 06:16 PM
    did you get this resolved? if not it is best to reach out to Aruba TAC.

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
    ------------------------------



  • 3.  RE: Virtual Gateway 10.3.1.1 in Azure deployment

    Posted Oct 26, 2022 03:03 AM
    Hi Ariyap,

    I've opened a TAC case and had a session with a support engineer. He should have come back to me yesterday, but as usual... nothing. Will contact him again today.

    Steven

    ------------------------------
    Steven Demets
    Solutions Architect
    Quant ICT
    https://quant.be
    ------------------------------

    Original Message


  • 4.  RE: Virtual Gateway 10.3.1.1 in Azure deployment

    Posted Oct 26, 2022 05:11 PM
    ok thanks.
    BTW what is the reason you are using Unmanaged mode of deployment?

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
    ------------------------------

    Original Message


  • 5.  RE: Virtual Gateway 10.3.1.1 in Azure deployment

    Posted Oct 27, 2022 03:05 AM
    Two reasons:
    1st, we manage Aruba Central for the customer, but not Azure. Giving Aruba Central access to Azure to create VMs, is not an option for the customer.
    2nd, because it gives us more flexibility in some of the choices that are made by Aruba Central in Azure. The orchestrator is fine, but its deployment is overkill for what we need, which drives the monthly cost higher. By doing a manual deployment we can tune at every step to only what we need, especially the storage and VM sizing.

    ------------------------------
    Steven Demets
    Solutions Architect
    Quant ICT
    https://quant.be
    ------------------------------

    Original Message


  • 6.  RE: Virtual Gateway 10.3.1.1 in Azure deployment
    Best Answer

    Posted Nov 03, 2022 10:05 AM
    My TAC contact escalated my issue with the engineering team and got the following response and workaround:


    "This is a known issue with 10.3 deployments on Azure . New VGW instance cannot be brought up directly on a 10.3 build. Only option available now is to create the instance using SDWAN-2.3 build and then upgrade to 10.3."


    I've done this using the ArubaOS_VGW_8.7.0.0-2.3.0.9_85196.vhd file from ASP. The virtual gateway came up without issue and downloaded it's config from Central. I then used Central to upgrade its firmware to 10.3.1.2.

    A reboot and some patience later, the virtual gateway is now connected to Central in version 10.3.1.2.

    Success!

    ------------------------------
    Steven Demets
    Solutions Architect
    Quant ICT
    https://quant.be
    ------------------------------

    Original Message


  • 7.  RE: Virtual Gateway 10.3.1.1 in Azure deployment

    Posted Nov 03, 2022 05:51 PM
    thanks for sharing

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba.
    ------------------------------

    Original Message


Related Content