NBAR Bit-rate

Unanswered Question

I'm trying to use the followin command on a 2801 (IOS 12.3.14) and on a 2811 (IOS 12.4.5)

show ip nbar protocol-discovery stats bit-rate top 10

Why does it show bit-rate information only at one of the interfaces?

Ex.:

Serial0/1/0

Input Output

----- ------

Protocol 30sec Bit Rate (bps) 30sec Bit Rate (bps)

------------------------ ------------------------ ------------------------

sqlnet 209000 13000

winmx 56000 0

skinny 7000 9000

custom-02 9000 0

notes 5000 1000

http 4000 1000

h323 2000 0

rtp 1000 0

netbios 0 0

custom-01 0 0

unknown 37000 28000

Total 330000 52000

Serial0/1/1

Input Output

----- ------

Protocol 30sec Bit Rate (bps) 30sec Bit Rate (bps)

------------------------ ------------------------ ------------------------

http 0 0

notes 0 0

rtp 0 0

skinny 0 0

winmx 0 0

custom-02 0 0

h323 0 0

netbios 0 0

custom-01 0 0

dns 0 0

unknown 0 0

Total 0 0

Thanks in advance

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Thank you for reply.

Yes.

Configuration following:

interface Serial0/1/0

no ip address

no ip redirects

no ip unreachables

ip nbar protocol-discovery

encapsulation frame-relay

ip route-cache flow

load-interval 30

no fair-queue

frame-relay traffic-shaping

frame-relay lmi-type cisco

frame-relay intf-type dce

!

interface Serial0/1/0.100 point-to-point

bandwidth 768

ip address x.x.x.x 255.255.255.252

frame-relay interface-dlci 100

class mpls-brr

frame-relay ip rtp header-compression

!

interface Serial0/1/1

no ip address

no ip redirects

no ip unreachables

ip nbar protocol-discovery

encapsulation frame-relay

ip route-cache flow

load-interval 30

no fair-queue

frame-relay traffic-shaping

frame-relay lmi-type cisco

frame-relay intf-type dce

!

interface Serial0/1/1.100 point-to-point

bandwidth 768

ip address x.x.x.x 255.255.255.252

frame-relay interface-dlci 100

class mpls-brr2

frame-relay ip rtp header-compression

Joseph W. Doherty Thu, 01/31/2008 - 04:20

Well that's curious.

I assume there is traffic passing across s0/1/1.

If you have software maintenance contract, you might try updating your IOS to latest patch level on the problem system.

Don't recall whether CEF required for the NBAR discovery feature, but if not active, you might try turning it on too.

Also don't recall whether the NBAR discovery command can be placed on the subinterface, but if it can, try removing it from the parent and see if that makes any difference.

Beyond that, unless some one else replies with another suggestion, might be a case for TAC.

That's really curious, I agree!

There's traffic passing across that serial. If I issue the

sh ip nbar protocol-discovery interface s0/1/1 command, I got the following output:

Serial0/1/1

Input Output

----- ------

Protocol Packet Count Packet Count

Byte Count Byte Count

30sec Bit Rate (bps) 30sec Bit Rate (bps)

30sec Max Bit Rate (bps) 30sec Max Bit Rate (bps)

------------------------ ------------------------ ------------------------

winmx 208252 307837

194214087 63208897

0 0

0 0

http 212177 48286

219609862 10675735

0 0

0 0

notes 140232 163147

96241551 76518715

0 0

0 0

rtp 963158 6603

64729736 410814

0 0

0 0

citrix 1 122152

132 55768975

0 0

0 0

------

As you can see, it doesn't show only Bit Rate and Max Bit Rate information.

CEF is required and is already configured. I've tried enable NBAR on the subinterface before, but it happened the same.

I think that I'm missing something else because I've tried that in two diferent routers with two different IOS versions, as I said at first post, and it doesn't work neither.

This is not a big deal, I'm just wondering why this happens...

Thank you

Joseph W. Doherty Thu, 01/31/2008 - 05:21

Double curious if two different routers behave this way.

On the other hand, if the two are the ones you noted in your original post, those with IOS 12.3.14 and 12.4.5, 12.3 is now up to 12.3.24a and 12.4 is now up to 12.4.18. Something worth trying, especially moving to a 12.3 (GD), if you can.

PS:

Actually if the 12.3.14 is a T, especially 12.3.14T or 12.3.14T1, both are deferred releases. Further, don't believe there's any 12.3 mainline release for 2800 series. Really worthwhile to move up to 12.4 mainline.

Actions

This Discussion