06-12-2006 02:48 AM
I am running ADSL on a 1700 router and trying to implement some application monitoring with Highlight. If I monitor the ethernet interface I can see all the in/out traffic without problems but when I try the same for the adsl interface I get mixed results. If I monitor on atm0 i get no data at all, if I monitor the dialer interface i get inbound data only and i can not get any stats for the atm sub-interfaces at all (even with nBar configured on them). Here is the config:
urrent configuration : 8950 bytes
!
!
version 12.3
service nagle
no service pad
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime show-timezone
service timestamps log datetime msec localtime show-timezone
service password-encryption
service linenumber
!
hostname xxxxxxxxxxxxxxxxxxx
!
boot-start-marker
boot-end-marker
!
logging buffered 16384 debugging
logging console emergencies
!
clock summer-time BST recurring last Sun Mar 1:00 last Sun Oct 1:00
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
ip subnet-zero
no ip source-route
!
!
ip tcp window-size 65496
ip tftp source-interface Loopback0
no ip domain lookup
no ip bootp server
ip cef
!
interface Loopback0
description Monitoring and Management
ip address xxxxxxxxxxxxxxxxxxxxxxx
!
interface ATM0
description xxxxxxxxxx
no ip address
ip nbar protocol-discovery
snmp ifindex persist
no atm ilmi-keepalive
dsl operating-mode auto
!
interface ATM0.1 point-to-point
ip nbar protocol-discovery
pvc DATA 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!
interface FastEthernet0
description xxxxxxxxxxxxxxxxxx
ip address xxxxxxxxxxxxxxxx
ip helper-address xxxxxxxxxxxx
no ip redirects
no ip unreachables
no ip proxy-arp
ip nbar protocol-discovery
ip tcp adjust-mss 1400
speed auto
no cdp enable
!
interface Dialer1
description xxxxxxxxxxxxxxxxxxx
mtu 1450
ip address xxxxxxxxxxxxxxxxxxxx
no ip proxy-arp
ip nbar protocol-discovery
ip rip advertise 15
encapsulation ppp
ip tcp adjust-mss 1400
dialer pool 1
no peer default ip address
no cdp enable
ppp max-bad-auth 3
ppp authentication chap xxxxxxxxxxx
ppp multilink
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer2 200
no ip http server
!
!
ip radius source-interface Loopback0
!
no cdp run
06-16-2006 10:18 AM
I believe nbar is a qos mechanism and not monitoring mechanism.
06-16-2006 11:43 AM
are you trying to monitor with snmp?
06-16-2006 03:49 PM
Since NBAR is an IP based technology I will not expect it to work on an interface that does not have routing enabled (it does not have an ip address). I will think that NBAR should be enabled on the dialer interface then.
As not having outbound traffic, I noticed that your default route points to dialer 2, which I did not find in your config. Is dialer the outbound interface from your route table, or is it going out through another interface? If another interface is the outbound interface, then you will not notice any outbound traffic from NBAR.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide