Thanks for these great videos they are very Helpful! I do have a question though,... often these examples use vlans where say vlan 14 is a VIOP or vlan 12 is guest etc,.. etc ... but often when trying to implement in an existing network you may have multiple voice vlans say Vlan 14 vlan 15 and vlan 16 , how could you approach this scenario?
With accept you can return vlan/ACLs/role that allow limited access; in this case to allow profiling. If you reject or drop, the client will not be allowed acces to the network at all and you can't really control it anymore.
Thanks for these great videos they are very Helpful!
I do have a question though,... often these examples use vlans where say vlan 14 is a VIOP or vlan 12 is guest etc,.. etc ... but often when trying to implement in an existing network you may have multiple voice vlans say Vlan 14 vlan 15 and vlan 16 , how could you approach this scenario?
What is the reason to set the enforcement profile to tie to deny access. why not accept or drop?
With accept you can return vlan/ACLs/role that allow limited access; in this case to allow profiling. If you reject or drop, the client will not be allowed acces to the network at all and you can't really control it anymore.
ok good