Ip accounting in Cisco Switch 3560 IOS-XR

[Nimilbabu007]

Hi Guys,

 I'm having a cisco 3560 switch in my office and DHCP servers are been configured on it and PC are connected towards that. I need Ip accounting and destination address Ip details to be monitored in case of excess bandwidth. Could you please suggest what should be configured inside the switch to monitor traffics?

[Mark Malone]

if its still supported on your ios version as its a deprecated command now legacy  , its been removed from ios-xe , still should be on the older 3560 switches though running old ios but in v15 it may not be there for you if your running that

netflow is what you should use now for data collection , not ip accounting and it would be verdsion 5 on  3560

if you can configure ip accounting all you do is set that on each interface you wish to monitor ...ip accounting

see doc

http://www.ciscopress.com/articles/article.asp?p=764234

[Nimilbabu007]

Hi Mark,

Ip accounting cannoit be enabled in the interface of the switch, we can user netflow but in IOX-XE netflow can be enabled by grouping them only. But i didnt get clear idea of creating the netflow group and adding them. Could you assist me on enabling netflow and other way for Enabling IP accounting.

Thanks,

Nimil

[Mark Malone · Accepted solution]

Hi

not sure what you mean by grouping them but here is how you deploy it , this is a working template off a switch of mine , there is no other way to deploy accounting though its legacy its netflow you use now in ios , if its not there its been removed

apply this under any layer 3 ip interface you want to collect data  off , set the destination collector and souorce interface usually a loopback, you can set the transport protocol if you wish depending again on your collector

under interface

ip flow monitor netflowtest input
ip flow monitor netflowtest output

in global config mode

flow record FLOW-RECORD
 description record to monitor network traffic
 match ipv4 tos
 match ipv4 protocol
 match ipv4 source address
 match ipv4 destination address
 match transport source-port
 match transport destination-port
 match interface input
 match interface output
 collect routing source as
 collect routing destination as
 collect routing next-hop address ipv4
 collect transport tcp flags
 collect counter bytes
 collect counter packets
 collect timestamp sys-uptime first
 collect timestamp sys-uptime last
!
!
flow exporter NetQos
 description export Netflow traffic to HQ
 destination x.x.x.x
 source xxxxxxxx
 template data timeout 300
 option interface-table timeout 1000
 option exporter-stats timeout 1000
!
!
flow monitor netflowtest
 description Used for ipv4 traffic analysis (Mapped To FLOW-RECORD)
 record FLOW-RECORD
 exporter NetQos
 statistics packet protocol

...........

to see of the router is collecting flows ....show flow exporter statistics

[Nimilbabu007]

thanks for the config's. i'll try it to my switches and check whether it's working or not.