Wired Intelligent Edge (Campus Switching and Routing)

Reply
Occasional Contributor I

8320 VSX Active Gateways vmac restriction

Hi,

 

I'm setting up a pair of 8320 with VSX and have approx 30 VLANs that i was trying to setup with active gateways. I've found there is a limitation of 16 vmacs, so i can't have a unique vmac on every activate gateway.

 

My question is, is it ok to have different active gateways with the same vmac and is there any downside to this.

 

Also if it is ok then why is it shown in the config examples in the Aruba guide as them having a different vmac per active gateway.


Accepted Solutions
Highlighted
MVP Guru

Re: 8320 VSX Active Gateways vmac restriction

Exactly. Use same active-gateway VMAC for all L3 VLAN interfaces.

View solution in original post


All Replies
Highlighted
MVP Guru Elite

Re: 8320 VSX Active Gateways vmac restriction

Hi,

 

You can reuse the same vmac for different vlan...



PowerArubaSW: Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP... More info

PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...) More info

PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)

PowerArubaIAP: Powershell Module to use Aruba Instant AP

PowerArubaMC: Powershell Module to use Mobility Controller / Master


ACMP 6.4 / ACMX #107 / ACCP 6.5 / ACSP
Highlighted
MVP Guru

Re: 8320 VSX Active Gateways vmac restriction

There is abolutely no downside of using same VMAC as the VMAC is purely link-local.

Would you have dual-NIC systems connected to the same VSX cluster,

you may want, for arp table clarity on server, to use different VMACs specifically for SVI (L3 VLAN i/f) used for such dual-zone servers.

Highlighted
Occasional Contributor I

Re: 8320 VSX Active Gateways vmac restriction

There will be no dual-homed servers, the setup will be utising mclags going to a 5130 IRF access switch stack and only ipv4 will be used.

 

This is the first VSX setup i've done and i'm still getting my head around it.

 

Are you saying the activate gateway vmac can be the same in each vlan as it's restricted to each vlans broadcast domain.

Highlighted
MVP Guru

Re: 8320 VSX Active Gateways vmac restriction

Exactly. Use same active-gateway VMAC for all L3 VLAN interfaces.

View solution in original post

Highlighted
Occasional Contributor I

Re: 8320 VSX Active Gateways vmac restriction

Thanks for clearing that up.

Highlighted
Occasional Contributor I

Re: 8320 VSX Active Gateways vmac restriction

Can anyone suggest what MAC can we use that by no chance will overlap with some other MAC address?
Is there any suggested range by Aruba?

 

Best regards,

Alon.

Highlighted
MVP Guru Elite

Re: 8320 VSX Active Gateways vmac restriction


@alonhav wrote:

Can anyone suggest what MAC can we use that by no chance will overlap with some other MAC address?
Is there any suggested range by Aruba?

 

Best regards,

Alon.


Yes, you can look Best Pratice guide : https://asp.arubanetworks.com/downloads/documents/RmlsZTplNzhhMzAxOC0yMmFhLTExZWEtOWYwMy00NzM4YTZiOGJhYWQ%3D



PowerArubaSW: Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP... More info

PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...) More info

PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)

PowerArubaIAP: Powershell Module to use Aruba Instant AP

PowerArubaMC: Powershell Module to use Mobility Controller / Master


ACMP 6.4 / ACMX #107 / ACCP 6.5 / ACSP
Highlighted
MVP Guru

Re: 8320 VSX Active Gateways vmac restriction

Hi! you would probably find this thread interesting (especially considerations reported on the latest reply, the one by @pv2b).

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: