Hey, how have you got devices listed directly in the navigation drop down? Is this an option somewhere? Or was this available on an older version of Central? All I get is Groups, Sites and Labels. It would be super handy to be able to jump between devices without dozens of clicks.
Is there any document/airheads broadcast, on how to setup a VPNC in Azure ? I'm trying to get a PoC setup at a customer and can't find any correct support from Aruba TAC or anywhere. I plan to spend one extra week trying to get something working before I classify this PoC as closed without success.
in the firmware upgrade for VPNC and all the branch gateway, is there a sequence that need to be follow or the upgrade can be triggered all at the same time?
It's all so straight forward. But, still struggeling with that GatewayPool, and SystemIP. So, you define a gateway-pool of 100.65.101.1 - 100.65.101.255 and connect it to vlan 4000. You then attatch this to the systemip and make it a gatewaypool. First question. This is defined on Aruba Central per /group, right? I dont see the subnet in your logical drawing. So how does central push this out? If this is a local network, and we have that behind a nat firewall how does it communicate? Another question is, why do you have a pool of 255 host? This pool is only for VPNC in your datacenter? Or is it for VPNC that are in the same group? If the default vlan is connected to vlan 4094, it get a IP from another DHCP subnet. ZTP comes in and it connects to Aruba central and download the configuration, it set a dhcp ip on vlan 4000 as system IP. But how would central communicate to that IP? I Get the whole ide, but this is something that confuses me. I asked the same question about Branch, do we also need to create a pool for switches, aps later on? Perhaps that's a different video. LOVE the videos! Sorry for my long question. /G
Copying this from the documentation: The system IP configuration is required on each Gateway provisioned in Aruba Central. Each Gateway uses one VLAN interface as its system IP address for communicating with network services such as RADIUS, syslog, TACACS+, and SNMP. help.central.arubanetworks.com/latest/documentation/online_help/content/gateways/cfg/system/gen-cfg-sys-ip.htm?Highlight=system%20ip The general idea is that you define a pool of these addresses for the aruba infrastructure. Since, there should be no overlap in these addresses, (And Central does not have a global gateway pool definition), I use different subnets per group (VPNC and BGW). This VLAN, like a loopback, will usually not be attached to an interface and will only be advertised as a route. The pool of the VPNC could have been smaller true :) Since VLAN 4000 is not attached to a physical port, it will only receive an IP-address from the scope defined in Central. Also, only gateways require such an IP-Address - so you do not need to configure this for switches or AP's.
The recommendation is that you would use a RF1918 private IP that is routable within your network. In Central you can define a pool of addresses (Gateway Pool) that are automatically assigned to the BGW's and VPNC's (1 address per device).
It is good to add that in many scenario's you would only configure 1 default gateway on the VPNC pointing to the Internet ISP. For the MPLS network you would configure a default gateway with a higher cost, if there is no internet connectivity.
Hey, how have you got devices listed directly in the navigation drop down? Is this an option somewhere? Or was this available on an older version of Central? All I get is Groups, Sites and Labels. It would be super handy to be able to jump between devices without dozens of clicks.
Is there any document/airheads broadcast, on how to setup a VPNC in Azure ? I'm trying to get a PoC setup at a customer and can't find any correct support from Aruba TAC or anywhere. I plan to spend one extra week trying to get something working before I classify this PoC as closed without success.
Also drawing a blank on the systemIP address. Is VLAN 4000 actually on the network? Or is it a magic VLAN like 4094, and 3333 ?
in the firmware upgrade for VPNC and all the branch gateway, is there a sequence that need to be follow or the upgrade can be triggered all at the same time?
if the VPNC is behind the firewall, how will the WAN interface be configured?
It's all so straight forward. But, still struggeling with that GatewayPool, and SystemIP. So, you define a gateway-pool of 100.65.101.1 - 100.65.101.255 and connect it to vlan 4000. You then attatch this to the systemip and make it a gatewaypool.
First question. This is defined on Aruba Central per /group, right? I dont see the subnet in your logical drawing. So how does central push this out? If this is a local network, and we have that behind a nat firewall how does it communicate?
Another question is, why do you have a pool of 255 host? This pool is only for VPNC in your datacenter? Or is it for VPNC that are in the same group?
If the default vlan is connected to vlan 4094, it get a IP from another DHCP subnet. ZTP comes in and it connects to Aruba central and download the configuration, it set a dhcp ip on vlan 4000 as system IP. But how would central communicate to that IP? I Get the whole ide, but this is something that confuses me.
I asked the same question about Branch, do we also need to create a pool for switches, aps later on? Perhaps that's a different video. LOVE the videos! Sorry for my long question. /G
Copying this from the documentation:
The system IP configuration is required on each Gateway provisioned in Aruba Central. Each Gateway uses one VLAN interface as its system IP address for communicating with network services such as RADIUS, syslog, TACACS+, and SNMP.
help.central.arubanetworks.com/latest/documentation/online_help/content/gateways/cfg/system/gen-cfg-sys-ip.htm?Highlight=system%20ip
The general idea is that you define a pool of these addresses for the aruba infrastructure.
Since, there should be no overlap in these addresses, (And Central does not have a global gateway pool definition), I use different subnets per group (VPNC and BGW).
This VLAN, like a loopback, will usually not be attached to an interface and will only be advertised as a route.
The pool of the VPNC could have been smaller true :)
Since VLAN 4000 is not attached to a physical port, it will only receive an IP-address from the scope defined in Central.
Also, only gateways require such an IP-Address - so you do not need to configure this for switches or AP's.
how do you identify what ip addres to be used in the system IP? does it need to be public only or we can use private IPs as well?
The recommendation is that you would use a RF1918 private IP that is routable within your network. In Central you can define a pool of addresses (Gateway Pool) that are automatically assigned to the BGW's and VPNC's (1 address per device).
It is good to add that in many scenario's you would only configure 1 default gateway on the VPNC pointing to the Internet ISP. For the MPLS network you would configure a default gateway with a higher cost, if there is no internet connectivity.