ak74,
If you leave the mgmt-VLAN as 1 (default), things should work.
However, if you have specific requirement to have mgmt-vlan as something else (in your case VLAN-6), then:
After quick-setup is done,
I believe you you will seeing something as below
(ArubaS3500-24T) #show running-config | begin 0/0/0
Building Configuration...
interface gigabitethernet "0/0/0"
switching-profile "Upstream-profile"
!
interface vlan "6"
ip address 172.16.252.50 255.255.252.0
!
(ArubaS3500-24T) # show interface-profile switching-profile Upstream-profile
switching profile "Upstream-profile"
------------------------------------
Parameter Value
--------- -----
Switchport mode trunk <<<<<<<<<<<<<
Access mode VLAN 1 <<<<<<<<<<<<<
Trunk mode native VLAN 1
Enable broadcast traffic rate limiting Enabled
Enable multicast traffic rate limiting Disabled
Enable unknown unicast traffic rate limiting Enabled
Max allowed rate limit traffic on port in percentage 50
Trunk mode allowed VLANs 1-4094
(ArubaS3500-24T) #show interface gigabitethernet 0/0/0 switchport extensive
GE0/0/0
Link is Up
Flags: Trunk, Trusted
Native VLAN is 1
VLAN membership:
VLAN tag Tagness STP-State
-------- -------- ---------
1 Untagged FWD <<<<<<<<<<<<<
1 Tagged FWD
6 Tagged FWD
As you can see from above, port 0/0/0 has native VLAN as 1, as a result , it allows un-tagged packets only for VLAN-1.
And is trunk-port for all other VLANs.
But, since your mgmt-IP is sitting on VLNA-6, packets (ARP-request) would go out as tagged (with 6)
Client / PC would anyway discard "tag"ness of the packet & would reply to ARP-request, which would be Un-tagged.
But target IP is sitting on RVI-6.
Looks like this is causing problem. also I beleive there was already internal bug reported on similar issue.
Not sure on that though...need to check with engineering team..... will get back on this.
Thanks,
-Vinay