Configuring Short-Lived Ip Protocol Filters - Avaya P550R User Manual Addendum

User Guide Addendum for the Avaya P550R and P880, v5.3.2

Configuring Short-Lived IP Protocol Filters

Overview
2
path to route packets of a specific short-lived protocol. And
by using the slow path to route short-lived protocol traffic,
you conserve the resources of the forwarding engines.
For information on how to configure short-lived protocol
filters, see "Configuring Short-Lived IP Protocol Filters"
page 2.
This feature helps conserve the forwarding engine resources of the
switch. Depending on the configuration of your network, the
forwarding cache may contain a high number of entries for short-
lived protocols, for example, DNS and NTP. These short-lived
protocol entries consume resources that could otherwise be used for
data traffic of other protocols such as FTP, Telnet, HTTP, RealAudio,
and online games.
If the forwarding cache contains a high number of short-lived
protocol entries, you can set the switch to use the slow path to route
packets of a specific short-lived protocol. By using the slow path to
route short-lived protocol traffic, you conserve the resources of the
forwarding engines, which provide the fast in band routing engine
(FIRE) and fast out of band routing engine (FORE). For information
about the slow path and FIRE and FORE paths, see "Routing
Overview" in Chapter 1, "Introduction," of the Avaya P550R, P580,
P880, and P882 Multiservice Switch User Guide, Version 5.3.1.
To configure short-lived protocol filters, your user account must be
assigned one of the following access types:
Read-write
Administrator
Custom access type that has read-write permission for the
routing feature
You can configure short-lived IP protocol filters only by using the
CLI. This feature is not available in the Web Agent or SNMP.
January 7, 2003
on
Part No. 610-0229-091