http://www.dslreports.com/forum/r20505439 en Wed, 20 Aug 2008 19:03:54 EDT Wed, 20 Aug 2008 19:03:54 EDT http://www.dslreports.com/forum/remark,20516424 panagioti9 : Not from what I can see, there aren't any issues. But it would be nice when you are trying to grasp network status to have something displaying what you think it should.
Thanks for all the responses.]]> http://www.dslreports.com/forum/remark,20516424 Wed, 21 May 2008 09:28:23 EDT http://www.dslreports.com/forum/remark,20514420 Da Geek Kid : This is highly due to the fact that the feature may not be set active or correct... Cisco does have tons of features that work but when it comes to displaying certain values, it may not fully function correctly... Again, that's just Show commands. But other than your Avg show looks you are NOT having any issues, correct?]]> http://www.dslreports.com/forum/remark,20514420 Tue, 20 May 2008 20:33:51 EDT http://www.dslreports.com/forum/remark,20513816 panagioti9 : I know...too much info confuses things. I just want to get a handle on how to manage bandwidth. I started by determining what type of traffic is on the network. My real problem at this point is, why does SNMP display Dialer1 inbound traffic but NBAR directly on the router itself, does not display the RDP traffic? Is there something I am missing here?]]> http://www.dslreports.com/forum/remark,20513816 Tue, 20 May 2008 18:28:20 EDT http://www.dslreports.com/forum/remark,20513431 Da Geek Kid : ok? so, what is your REAL issue here?]]> http://www.dslreports.com/forum/remark,20513431 Tue, 20 May 2008 17:09:18 EDT http://www.dslreports.com/forum/remark,20513162 panagioti9 : Here is some more consistent inconsistency.(I just turned on protocol discovery for this particular router 10 minutes before)

sh ip nbar protocol-discovery stat byte-count protocol rdp

Ethernet0
Input Output
----- ------
Protocol Byte Count Byte Count
------------------------ ------------------------ ------------------------
rdp 895138 5044546
unknown 76220 79759
Total 1019470 5160126

Dialer1
Input Output
----- ------
Protocol Byte Count Byte Count
------------------------ ------------------------ ------------------------
rdp 0 1091328
unknown 0 90961
Total 84984 1186349]]> http://www.dslreports.com/forum/remark,20513162 Tue, 20 May 2008 16:23:46 EDT http://www.dslreports.com/forum/remark,20513134 panagioti9 : Notice how the diealer1-rdp-input doesn't come anywhere near to matching the number of ethernet0-rdp-output.(or not at all)

>sh ip nbar protocol-discovery stat bit-rate top-n 5

Ethernet0
Input Output
----- ------
Protocol 5min Bit Rate (bps) 5min Bit Rate (bps)
------------------------ ------------------------ ------------------------
rdp 15000 30000
dhcp 0 0
ntp 0 0
bgp 0 0
cuseeme 0 0
unknown 1000 1000
Total 16000 31000

Dialer1
Input Output
----- ------
Protocol 5min Bit Rate (bps) 5min Bit Rate (bps)
------------------------ ------------------------ ------------------------
rdp 0 15000
icmp 1000 0
ssh 0 0
snmp 0 0
ntp 0 0
unknown 0 1000
Total 1000 16000]]> http://www.dslreports.com/forum/remark,20513134 Tue, 20 May 2008 16:19:21 EDT http://www.dslreports.com/forum/remark,20511602 Da Geek Kid : post your show ip nbar prot]]> http://www.dslreports.com/forum/remark,20511602 Tue, 20 May 2008 12:07:57 EDT http://www.dslreports.com/forum/remark,20510458 panagioti9 : Yes, e0 outbound goes to the LAN behind the router, the "RDP clients". I have protocol discovery turned on for the e0 and di1 interfaces just to confirm the direction of the traffic, but it doesn't make sense to me. If an RDP client behind these 837/877's has RDP traffic coming inbound from my LNS. Shouldn't the RDP traffic go inbound on Dialer1 and outbound on Ethernet0? SNMP stats show this pattern but NBAR does not, which is why I am thinking I am doing something wrong. ]]> http://www.dslreports.com/forum/remark,20510458 Tue, 20 May 2008 07:25:41 EDT http://www.dslreports.com/forum/remark,20509372 Da Geek Kid : ok just to make sure, E0 Outbound is leaving the router towards the LAN.
NBAR is always on. The ip nbar pro allows you to do sh ip nbar protocol-disvovery.

The way you have configured the class automatically states to use NBAR.

I would also suggest to create a THIN-2... here's why, Dialer outbound is leaving the rooter to the net and E0 outbound is leaving the roooter to the LAN... so I would separate their Policy]]> http://www.dslreports.com/forum/remark,20509372 Mon, 19 May 2008 22:43:04 EDT http://www.dslreports.com/forum/remark,20505439 panagioti9 : OK...so i am puzzled. Here is my story. I have a WAN, where I administer my own LNS to provision DSL for my clients(which I also administer). I have been attempting to configure QOS at the client end (using Cisco 837's and 877's). I have NBAR support enabled with protocol-discovery enabled on my Dialer1 and Ethernet0 interfaces(and ATM0 just for the heck of it). My typical client network traffic scenario is clients launching RDP traffic behind the Cisco 837/877's. Thus I would like to know:
1) Is it possible to apply a policy for RDP traffic coming back INBOUND on the 837/877's and if so how?
2) Why is it that SNMP statistics show Dialer1 displaying traffic inbound on Dialer1 and outbound Ethernet0(all matching RDP traffic stats) but sh ip nbar protocol stats bit-rate top-n does NOT. For example, I see Ethernet0 outbound displaying 200kbps of RDP traffic, but the interface that traffic "supposedly" came into the router, through Dialer1, shows no traffic at all for RDP.

Please let me know if my understanding of QOS is even correct. I simply want to be able ensure that RDP traffic gets what it needs.

Attached is what should be the pertinent config info

c837-samp.txt 1,374 bytes

]]> http://www.dslreports.com/forum/remark,20505439 Mon, 19 May 2008 09:51:14 EDT