I would like to use a dead vLAN as the native/untagged vLAN on trunk feeds as a security best practice. The trunk feed is between a Cisco and Aruba switch. On Cisco switch, the vLAN is left out of the vLAN database and frames won't get forwarded, making it "dead". The dead vLAN is native on the Cisco trunk interface. However on the Aruba switch it is required to have the vLAN defined before it can be added untagged on the interface. This makes me nervous that this vLAN would be forwarding frames and potentially cause loops or large broadcast domains.
Aruba switches will allow "no untagged vLAN" to be specified. However, I'm pretty sure that will create a vLAN mismatch to a Cisco switch, which requires a native vLAN to be specified.
What is the best way to create a "dead end" vLAN on Aruba/HP switches, so that no traffic is forwarded?