Thanks, that looks nice.
BTW, I would recommend to use Named VLANs for this purpose as @Sietze Reitsma suggests in this post. It will make your policy much more readable than having these decimal VLAN values.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Dec 20, 2023 07:31 AM
From: PK97
Subject: Egress-VLANID
As the conversion for the values is very tedious, I have created a small website with javascript to generate a valid Enforcement Profile XML:
You can enter the VLAN ID, choose if tagged/untagged and optionally add the device-mode port-mode as this is often used with APs.
https://philipp-koch.net/cppm/rfc4675.html
------------------------------
Philipp Koch | Senior Technical Consultant @ Bohnen IT | ACDX | ACEP | Germany
Original Message:
Sent: Jul 11, 2016 10:03 AM
From: Herman Robers
Subject: Egress-VLANID
What works is when you convert the hex value back into decimal...
So, for vlan 123, convert to hex is 0x07b (this tool will work: http://www.rapidtables.com/convert/number/decimal-to-hex.htm)
Prepend 0x31000 for tagged, and get 0x3100007b.
Now convert back 0x3100007b back to decimal (use http://www.rapidtables.com/convert/number/hex-to-decimal.htm) which will result in 822083707.
Use 822083707 ias value n your Hewlett-Packard-Enterprise:HPE-Egress-VLAN-ID attribute to return VLAN 123 tagged.