From: Neil McKee (neil_mckee@inmon.com)
Date: 07/09/02
Traffic Server version 2.2.16
is now available for download. This represents a significant advance
over version 2.1. Here are just a few of the changes:
Highlights
* Periodic Reports: Reports can now be scheduled to run
automatically during the night. (see below).
* IPv6: Support for IPv6 top-talkers and traffic matrices.
* Long Minute History: The "KeepActiveMinutes" setting can now be
set and overridden anywhere in the configuration file. This allows
long, full-detail traffic histories to be kept for selected
devices or selected links.
* IP Address Mappings: New algorithm works with virtual hosts,
allowing them to be located to their switch port by name.
* Filtering: New filtering options allow '!' to be used as logical
NOT, and now subnet-lists can be referenced using convenient
<site>:<zone>:<subnet> notation. (see below).
* Port Names: SNMP variables can be used to name ports
automatically (see below).
* Performance: A number of performance bottlenecks have been
removed, and we have switched to a new servlet engine and java
virtual machine. You should find this version more responsive.
For an extensive list of the changes, see the "Release Notes" link
from the upgrade page.
Periodic Reports
The new reporting scheme allows HTML report "templates" to be uploaded
to the Traffic Server. These templates can contain special HTML tags to
indicate where charts and tables should be inserted. The Traffic Server
will process these templates every night and generate static HTML pages
for each one, plus an overall index. This allows report pages to be
served instantly. For more details on how to customize this for your
requirements, see the tutorial "Creating Your own Reports" at
http://www.inmon.com/tutorial.htm
Filtering
When entering a filter on source address or destination address, you can
now invert the sense of the filter by adding a '!' character at the
beginning. For example, setting
sourceAddress=!128.141.122.0/24,128.141.123.0/24 means the source
address must not be in the 128.141.122.0/24 subnet or the
128.131.123.0/24 subnet.
When filtering on IPv4 addresses, you can now identify a list of subnets
using the names from the configuration file. The format is
"site:zone:subnet". For example, if you have a [subnet] called
"backup1" in a [zone] called "backup LAN" on the [site] called "New
York" then you use could use any of the following filters:
sourceAddress = New York:backup LAN:backup
sourceAddress = New York:backup LAN:
sourceAddress = New York::
(Note that you can leave out the zone or subnet, but you must always
have two ":" characters). So to look at traffic that is going from New
York to the rest of the world, you can set sourceAddress=New York:: and
destinationAddress=!New York::.
Port Names
Sometimes knowing the ifIndex of a port is not enough. It is often more
helpful to know the physical card+slot information. Now you can use a
standard SNMP MIB variable to automatically assign port names. Just set
portNames = ifName anywhere down to the [agent] level of the config file
(other choices for this setting are ifDescr or ifAlias). If you still
need to set some names manually, the name = <string> setting in a [port]
section will still take precedence.
Please send your feedback and suggestions. If you hit "reply" your
message will go to the mailing list and be logged in the discussion group.
-- --------- Neil McKee mailto:Neil_McKee@InMon.com <mailto:Neil_McKee@InMon.com>InMon Corp. http://www.InMon.com
This archive was generated by hypermail 2.1.4 : 07/09/02 PDT