Avaya Configuring Frame Relay Services Manual de usuario descargar pdf (Pagina 53)

Frame Relay Overview

117376-B Rev. 00 2-27

The FECN and BECN notiﬁcations are part of the header in a frame relay data

packet. In a big pipe/little pipe topology (see F

igure 2-10), the central site router

typically sends much more data than it receives. Therefore, the remote site routers

that receive a lot of trafﬁc may be getting large numbers of FECNs, while the

central site router is getting relatively few data packets, and therefore few BECNs,

and is unaware than congestion is occurring. You may need to ﬁne tune the

Congestion Counter and Congestion Timer parameters (see A

ppendix A, “Site

Manager Parameters”), from the default values of 20 FECN or BECN counts per

second to, for example, 10 counts per 5 seconds to account for the differences in

trafﬁc volume from and to the central site.

Figure 2-10. FECNs and BECNs in Big Pipe/Little Pipe Topology

X.213 Priority for SVCs

Some frame relay networks that support SVCs can prioritize SVC data and

connection characters by setting X.213 priority parameters. You conﬁgure values

for these parameters at the router, and the frame relay network uses them. See

“Setting X.213 Pr

iorities for SVCs,” in Chapter 3, “Customizing Frame Relay,”

for instructions on conﬁguring X.213 parameters.

Inactivity Timing for SVCs

The Inactivity Timer and Inactivity Timer Mode parameters combine to

automatically disconnect an SVC according to values that you conﬁgure for

amount of time and the direction that data is ﬂowing over the SVC. You can

conﬁgure these parameters to apply to all SVCs in a service record, and you can

also conﬁgure them for individual SVCs.

FR0015A

Remote site B

Remote site D

Remote site C

Flow of most traffic

Central site A

BECNs (few)

FECNs

(many)

1 2 ... 48 49 50 51 52 53 54 55 56 57 58 ... 161 162

Sin comentarios

Avaya Configuring Frame Relay Services Manual de usuario Pagina 53