The 3 step process is correct but since you are matching the traffic destined to the server with precdence as critical ,how are you marking the traffic as critical and how do u differentiate the traffic destined to the server as critical and non critical.
I feel you have got some application on that server which you want to access over the WAN.
Then i feel simple ACL matching the source network(ur local lan) and the destination server ip is enough to be precise u can use the TCP option to define the port as you have already done ..
Just a question on this. Why do I have to configure the "shape average 192000" on the second policy map ?. I have a frame relay with 128K Access and 64K PVC and I want the traffic to use the whole PVC-64K when there is traffic between 10.1.104.0/24 to 10.1.85.149 on port 80.
I have tried this and when I do a "show access-list" there is no match. I then apply this command to the serial interface(not sub interface):
"service-policy output fmis-policy" I didnt use "temp" but use "fmis-policy" as the name of the first policy map
Then I manage to see the ACL counters for the first ACL.Didnt see
Thank you very much. I have solve the problem using your solution. I was also having problem because of the old IOS version on the remote router which I beleive doesnt support QoS. That is the reason why I couldnt apply the "service policy output" command on the map-class.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...