Unsolved
This post is more than 5 years old
5 Posts
0
12385
PC5548 IP ACL
I'm setting up a 5548 policy to prioritise voice traffic on a vlan. I've been working through the "Configuring Dell PowerConnect 55xx series switch voice VLAN" document.
When setting up the IP ACL, the documented command is
ip access-list extended voip
permit ip any 192.168.10.0 0.0.0.255
The policy with this acl is attached to a trunk port and the device port (PBX in this case). Assuming the PBX is on the 192.168.10 subnet I can see the logic with the ip access list on the trunk prioritising any data TO the PBX subnet.
What about the port the PBX is on though? The document applies the same acl via the policy.
Shouldn't the acl be reversed in this case?
ip access-list extended voip_from_pbx
permit ip 192.168.10.0 0.0.0.255 any
So that any data FROM the PBX is then prioritised?
Or am I missing how the ACLs work?
Cheers
Al.
al7009
5 Posts
0
October 23rd, 2012 00:00
I've setup the ACL on my switch like:
ip access-list extended voip
permit ip any 192.168.10.0 0.0.0.255
permit ip 192.168.10.0 0.0.0.255 any
So that traffic to and from the ports is prioritised whether trunk, general or access.
I then setup the Queue Statistics in the web admin tool to see what was hapenning in queue 6.
Before I did the above, queue 6 had almost no packets. most went to queue 1 even though only an IP phone is on the port.
Now, most go to queue 6 - which is more like what I would expect.
Cheers
Al.