SD-WAN

I am still a little confused about the concept of the system IP address

In it said to be important for Gateways and microbranches

One thing I don't understand is that some documentation states that VLAN 4087 is reserved for this purpose while other airhead videos use a different VLAN for this, and you can also use a Loopback interface.

Being familiar with Loopback and its purpose for many other vendors, why at all use VLAN 4087 or any other VLAN for that matter, and just use a Loopback interface? 

Also would defining both a Loopback and a system IP be redundant?

Thanks

you can use any VLAN ID as a system IP.

You can also use loopback

check the Aruba SD-Branch Fundamentals Guide

I am still a little confused about the concept of the system IP address

In it said to be important for Gateways and microbranches

One thing I don't understand is that some documentation states that VLAN 4087 is reserved for this purpose while other airhead videos use a different VLAN for this, and you can also use a Loopback interface.

Being familiar with Loopback and its purpose for many other vendors, why at all use VLAN 4087 or any other VLAN for that matter, and just use a Loopback interface? 

Also would defining both a Loopback and a system IP be redundant?

Thanks

Hi Ariy-,

thank you for responding, however it feels a little like an echo of my question. I understand I can use both. I guess I can draw the conclusion that the Aruba guides could benefit from simplification.  My conclusion is you can use any IP address and if you are used to using loopback addresses stay consistent with that. 
is it true though is VLAN 4087 reserved on gateways?

https://www.arubanetworks.com/techdocs/central/2.5.2/content/gateways/cfg/bgw-dev-system-page.htm

you can use any VLAN ID as a system IP.

You can also use loopback

check the Aruba SD-Branch Fundamentals Guide

I am still a little confused about the concept of the system IP address

In it said to be important for Gateways and microbranches

One thing I don't understand is that some documentation states that VLAN 4087 is reserved for this purpose while other airhead videos use a different VLAN for this, and you can also use a Loopback interface.

Being familiar with Loopback and its purpose for many other vendors, why at all use VLAN 4087 or any other VLAN for that matter, and just use a Loopback interface? 

Also would defining both a Loopback and a system IP be redundant?

Thanks

even the current Central doco states that.

It is reserved for the guided BGW workflow to make it easier I suppose. But again you can use any interface.

also for example If you use a VLAN pool for system-ip, it is basically dynamically creating loopback interface. 

Hi Ariy-,

thank you for responding, however it feels a little like an echo of my question. I understand I can use both. I guess I can draw the conclusion that the Aruba guides could benefit from simplification.  My conclusion is you can use any IP address and if you are used to using loopback addresses stay consistent with that. 
is it true though is VLAN 4087 reserved on gateways?

https://www.arubanetworks.com/techdocs/central/2.5.2/content/gateways/cfg/bgw-dev-system-page.htm

you can use any VLAN ID as a system IP.

You can also use loopback

check the Aruba SD-Branch Fundamentals Guide

I am still a little confused about the concept of the system IP address

In it said to be important for Gateways and microbranches

One thing I don't understand is that some documentation states that VLAN 4087 is reserved for this purpose while other airhead videos use a different VLAN for this, and you can also use a Loopback interface.

Being familiar with Loopback and its purpose for many other vendors, why at all use VLAN 4087 or any other VLAN for that matter, and just use a Loopback interface? 

Also would defining both a Loopback and a system IP be redundant?

Thanks