Avaya Configuring Traffic Filters and Protocol Prioritization Bedienungsanleitung PDF herunterladen (Seite 28)

Configuring Traffic Filters and Protocol Prioritization

1-8

• The upper-level protocol header. Examples of protocol header types include:

— IP and TCP

— Source route bridge

— DLSw

• User data

Each criterion is deﬁned by a byte length and an offset from a known reference

point within the protocol’s DLC and protocol headers. .

Predeﬁned and User-Deﬁned Criteria

The Conﬁguration Manager provides a selection of default (predeﬁned) ﬁlter

criteria for each supported protocol. Or, you can deﬁne a ﬁlter criterion based on

speciﬁc bit patterns contained in a packet’s header (user-deﬁned criteria). One

ﬁlter can employ multiple criteria, including a combination of predeﬁned and

user-deﬁned criterion, to ﬁt a site’s trafﬁc patterns.

All trafﬁc ﬁlter criteria are based on common bit patterns in the packet headers of

supported protocols (reference points). Every trafﬁc ﬁlter criterion includes the

length of the ﬁltered pattern and an offset from a known reference point. The

trafﬁc ﬁlter uses this information to locate the part of the packet to examine.

Predeﬁned ﬁlters use predeﬁned offsets and lengths. You specify the criteria

length and offset from a known reference point when creating user-deﬁned

criteria.

Predeﬁned Criteria

For bridge trafﬁc, predeﬁned criteria are part of the Data Link Control (DLC)

header. For routed trafﬁc, a predeﬁned criterion can be part of the DLC header or

part of an upper-level network protocol header. Table 1-2 summarizes the

predeﬁned inbound trafﬁc ﬁlter criteria for supported protocols. Table 1-2

summarizes the predeﬁned outbound trafﬁc ﬁlter criteria.

1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 161 162

Keine Kommentare

Avaya Configuring Traffic Filters and Protocol Prioritization Bedienungsanleitung Seite 28