05-17-2012 03:56 PM - edited 03-07-2019 06:46 AM
Hello,
I'm wondering what the correct process would be to mark traffic for say an snmp monitoring server. I have some links that get over utilized regularly and my snmp traffic cannot make it through and gives me false positives. I have set the snmp-server ip dscp xx on the switches and I can see that the markings are happening and going out of the switch.
!
snmp-server ip dscp 30
!
dscp: outgoing
-------------------------------
0 - 4 : 172300578 0 0 0 74
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 16853 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 3516 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
So the marking is happening and the traffic is prioritized. Now, what I think is happening is that the snmp server is not getting its requests to the switch because the link is over utilized. So I need to mark the traffic on the server end? This server is on a VMWare host, and I am wondering what the best process is to mark traffic from a guest vm server connected to a 3560?
Set the dscp marking on the server itself and then just trust dscp on the trunk port to the vmware host? Or mark the traffic on the switch using a policy map?
Thanks,
Dan.
05-17-2012 05:18 PM
Hi,
Maybe you can try something like this:
The default COS coming from the guest vm server is 0 (default). Now, on the uplink port on your 3560, you can try rewriting the COS using:
switchport priority extend cos 5
and see if this helps.
HTH
05-17-2012 05:32 PM
Hmmm, don't think I want to do that because there are many more guests on that host and that would mean that all of the guests traffic is marked with cos 5.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: