Wired Intelligent Edge (Campus Switching and Routing)

Reply
Highlighted
Occasional Contributor II

ArubaOS-CX 8320 VLAN ID 4094

Hi,

 

I'm trying to understand why the 8320 doesn't let me use the ID 4094.

 

As per docs, pg 21 Aruba 8320 Layer 2 Bridging Guide for ArubaOS-CX 10.01 just the IDs VLAN 1-4040 are avaliable.

Version : TL.10.00.0008
Build Date : 2018-02-15 11:00:41 PST
Build ID : ArubaOS-CX:TL.10.00.0008:4d4e3b0caef5:201802151853
Build SHA : 4d4e3b0caef546ab5e2b6a4e4c99e8947b55fdff
Active Image : secondary

We have the ID 4094 as the management VLAN. The old 5500 use this ID for management.

Is there any workaroud?

 

 


Accepted Solutions
Highlighted
MVP Guru

Re: ArubaOS-CX 8320 VLAN ID 4094

Hello,

Yes, this is correct.

On 8320: 1-4040 can be used for VLAN. 4041-4094 are reserved VLANs and can't be used for any purpose than what they are reserved for.

On 8400: 1-4094 can be used. Reserved VLANs are in a separate range (8000~, you may see that range using the API to list the VLANs).

 

This is no workaround to use 4094 on 8320.

Regards,

Vincent

View solution in original post

Highlighted
MVP Guru

Re: ArubaOS-CX 8320 VLAN ID 4094

This is because they are used internally. That being said, it is good feedback and there is on-going CLI improvment to get better clarity.

 

Regards,

Vincent

View solution in original post


All Replies
Highlighted
MVP Guru

Re: ArubaOS-CX 8320 VLAN ID 4094

Interesting, it looks like the admitted range is really 1-4040...I noticed that the creation of any VLAN from 4041 to 4094 is not permitted (is the range 4041-4094 internally reserved?) providing the message you saw "Ignoring the operation on internal VLAN(s) x" where x is any VLAN between 4041 included and 4094 included.

Highlighted
Occasional Contributor II

Re: ArubaOS-CX 8320 VLAN ID 4094

So, you beleve that I cannot use the 4094 for management VLAN?

 

There are quite a few switch using the 4094 as management VLAN. Is there any workaround?

Highlighted
MVP Guru

Re: ArubaOS-CX 8320 VLAN ID 4094

Hello,

Yes, this is correct.

On 8320: 1-4040 can be used for VLAN. 4041-4094 are reserved VLANs and can't be used for any purpose than what they are reserved for.

On 8400: 1-4094 can be used. Reserved VLANs are in a separate range (8000~, you may see that range using the API to list the VLANs).

 

This is no workaround to use 4094 on 8320.

Regards,

Vincent

View solution in original post

Highlighted
Occasional Contributor II

Re: ArubaOS-CX 8320 VLAN ID 4094

Interesting that we can't find any information for what reason there are reserved VLANs on 8340.

 

The next test I'm going to do is to check if it can a least "pass the tag" to a trunk port from one switch to another.

Highlighted
Occasional Contributor II

Re: ArubaOS-CX 8320 VLAN ID 4094

Just to let you know.

 

It doesn't pass any traffic on 4094.

Highlighted
MVP Guru

Re: ArubaOS-CX 8320 VLAN ID 4094


@vincent.giles wrote: On 8320: 1-4040 can be used for VLAN. 4041-4094 are reserved VLANs and can't be used for any purpose than what they are reserved for.

Hello Vincent, that's interesting...just curious, a question: why then on Aruba 8320 the show capacities vlan-count CLI Command (which is supposed to show the maximum number of VLANs supported in the system) still outputs 4094?

Highlighted
MVP Guru

Re: ArubaOS-CX 8320 VLAN ID 4094

This is because they are used internally. That being said, it is good feedback and there is on-going CLI improvment to get better clarity.

 

Regards,

Vincent

View solution in original post

Highlighted
MVP Guru

Re: ArubaOS-CX 8320 VLAN ID 4094

There will be an update on this thread for reserved-vlan in a couple of weeks.

Highlighted
MVP Guru

Re: ArubaOS-CX 8320 VLAN ID 4094

In 10.5, internal VLANs range is now configurable.