Thursday, January 26, 2006

Creating report from packetshaper units.

Still trying compile information from reports generated from a couple of packeteer units that were brought back from a customer's offices. One wasi n New Haven Connecticut and the other was in Bohemia Long Island. As much a I like to write, trying to get these reports right on is a pain. Since they are going to be billed, the report has to look and sound perfect. Sometimes when I do this stuff I think I'd rather be troubleshooting computer desktop or network problems instead. For those of you who have not had the opportunity to use the packeteer products, I've definitely have to give them a thunbs up. They make some good stuff, pricy but the data you can retrieve and the traffic shaping they could so on a very granular level is excellent. You know, I just remembered that the reason I'm doing t his report is to troubleshoot a problem. The one thing I have to mention about the packeteer remporting, and I hope they fix this, is that if the year changes over like it just di from '05 to '06, You can't get granular reports. The end date for the report has no year field so the report comes up blank because it's looking into the current year's future.


jeff reed said...

I've used packeteer products before. Their older models are slow in compa3ison to today)s when trying to change from one page to another using their web front end. A person more skilled at using the packeteer command line will not really have a problem with the speed. For customers, the reports are really useful in terms of information and appearance.
I believe there should have been some basic templates for reports for using the packeteers on networks to gather information about protocols in use and the bandwidth usage by each of the protocols discovered.

Anonymous said...

I agree, a few templates would have been handy in the older models. These units can gather a lot of data. Some general reports for most common requests would have been handy.