Article View: comp.dcom.sys.cisco
Article #354Cisco IP Accounting
From: Michael (NMI) Dorl
Date: Mon, 31 Aug 1992 21:54
Date: Mon, 31 Aug 1992 21:54
63 lines
2641 bytes
2641 bytes
The following message describes a problem we are facing.
If you have solved it with non-Cisco equipment, are
interested it it, or would like to see Cisco implement
the proposed changes, we'd like to hear from you.
WiscNet is a IP network serving Wisconsin colleges and
universities. Members are connected with Cisco routers.
Each member is connected through an ethernet interface
on some WiscNet provided cisco router. In general, the
Cisco provided traffic statistics for these ethernet
interfaces provide excellent information on traffic
to/from the members. Some members have extended the
network to non-members through connections we call
backdoors. WiscNet has a need to measure this backdoor
traffic on a network by network basis.
Although Cisco does provide some IP accounting, it is
not suitable for this need because...
The information gathered is too detailed. You can
select which networks to do accounting for with a
access list but once selected, the router does
accounting on a source destination IP pair basis.
Thus separate accounting entries are kept for
potentially hundreds or thousands of IP
source/destination pairs.
Only packets flowing out are accounted for. Thus to
get a total picture for a given network number, one
must enable accounting on all interfaces on a router.
What we'd like to see might be effected by a change to
the IP ACCOUNTING-LIST command.
IP ACCOUNTING ip-address mask keywords
where keywords could be
SUMMARY
make a single summary entry for matching packets.
IN
include incoming packets
OUT
include outgoing packets
SUMMARY accounting entries have the ip-address (from the
IP ACCOUNTING-LIST command) in either the source or
destination address and zero in the other address.
This would allow one to measure traffic to/from specified
networks while using only two accounting entries
minimizing search time and buffer resources. It would
also allow all accounting for a network to be done on a
single interface rather than router wide.
Michael Dorl (608) 262-0466 fax (608) 262-4679
dorl@vms.macc.wisc.edu MACC / University of Wisconsin - Madison
dorl@wiscmacc.bitnet 1210 W. Dayton St. / Madison, WI 53706
Technical Details
Message-ID:
<22083116541825@vms3.macc.wisc.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!sun-barr!ames!agate!boulder!recnewsShow Full Headers
Complete Article Headers
Newsgroups: comp.dcom.sys.cisco Path: arc1-ca.pugleaf.net!sparky!uunet!sun-barr!ames!agate!boulder!recnews From: "Michael (NMI) Dorl" <DORL@macc.wisc.edu> Subject: Cisco IP Accounting Message-ID: <22083116541825@vms3.macc.wisc.edu> Sender: news@colorado.edu Date: 31 Aug 92 16:54 CDT X-Vms-To: IN%"CISCO@SPOT.COLORADO.EDU",DORL Lines: 63