Wilson,
Isso. J� trabalhei com o Passport(PP) da Nortel e com o DPN tb. Na
pr�tica, o mesmo descarta CIR no momento de congestionamento "pesado". Mas �
um equipamento muito bom. Um detalhe fora do escopo. A comunica��o entre os
PP e DPN pode ser realizada via protocolo propriet�rio chamado UTP(universal
transfer protocol). No IGX(equipamento SW Wan - Fr e ATM) existe tambem o
protocolo Fast-Packet.
Tks
Jorge Francisco de Souza Silveira
Opera��es - Dados & Internet
AT&T Latin America
Rua da Candel�ria, n� 65, Salas 2201 e 2301
Cep 20091-020 - Rio de Janeiro - RJ
Tel.: +55(21) 223-7050 - Fax: (21) 518-8105
[EMAIL PROTECTED]
http://www.attla.com.br <http://www.attla.com.br/>
-----Mensagem original-----
De: Wilson Chicolet [mailto:[EMAIL PROTECTED]]
Enviada em: Quarta-feira, 3 de Janeiro de 2001 09:11
Para: Lista de Discuss�o Rede Wan
Assunto: RE: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
Jorge,
Quanto a primeira pergunta: Equipamento Passport 7480 da Nortel Networks,
Quanto a segunda: Se a rede da Prestadora Frame Relay entrar em
Congestionamento at� o que est� garantido no CIR � descartado, esse o motivo
de se configurar traffic shaping nos Ciscos, para fazer uma "desacelera��o
de pacotes" atrav�s dos bits de BECN/FECN.
Abra�os,
Wilson Chicolet
-----Original Message-----
From: Silveira, Jorge [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ]
Sent: Tuesday, January 02, 2001 8:27 PM
To: Lista de Discussco Rede Wan
Subject: RES: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
Wilson,
Qual era o equipamento telefonica???(responda se puder e souber!!!)
Chegou a perguntar ao Instrutor se CIR tb era descartado??
Obrigado pela tua informa��o.
Tks
Jorge Francisco de Souza Silveira
Opera��es - Dados & Internet
AT&T Latin America
Rua da Candel�ria, n� 65, Salas 2201 e 2301
Cep 20091-020 - Rio de Janeiro - RJ
Tel.: +55(21) 223-7050 - Fax: (21) 518-8105
[EMAIL PROTECTED]
http://www.attla.com.br <http://www.attla.com.br> <
http://www.attla.com.br/ <http://www.attla.com.br/> >
-----Mensagem original-----
De: Wilson Chicolet [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ]
Enviada em: Quinta-feira, 28 de Dezembro de 2000 09:32
Para: Lista de Discuss�o Rede Wan
Assunto: RE: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
Jorge,
Na �ltima empresa que trabelhei (Prodesp), participei da implanta��o e
tamb�m opera��o e manuten��o da Rede Frame Relay com a Concession�ria
Telef�nica. Nessa rede tinhamos dois circuitos de 2Mbps no Site Central e
velocidades distintas nos sites usu�rios, como 256, 128 e 64Kbps. O CIR
escolhido foi pelo famoso m�todo do chutometro tupiniquim: Velocidade
nominal dividida por dois. Tinhamos tamb�m configurado o bandwidth por
sub-interface, mas n�o tinhamos o traffic shaping configurado.
Sempre que podia fazia comandos show frame-relay pvc XXX nos roteadores dos
usu�rios, e verificava que sempre estavam incrementando os campos DE (Pacote
Eleito para Descarte em caso de congestionamento na Rede Frame Relay) e o
BECN e FECN. Quando fiz um curso com um instrutor CCIE da Empresa Softnet da
Argentina (Miguel), ele falou que se n�o fosse usado o Traffic Shaping nos
roteadores Cisco, pelo cen�rio apresentado a ele como neste E-mail, haveria
o descarte de pacotes pelos Switches da Operadora do servi�o Frame Relay e
que s� o usu�rio perceberia pela interrup��o do servi�o utilizado, como por
exemplo o acesso a WEB.
Como n�o tinhamos um Analisador de Dados dispon�vel, n�o conseguia fazer uma
monitora��o das WANs, para verificar o que acontecia. Foi uma pena, pois
poderia ter aprendido muito mais do que sei hoje.
Abra�os,
Wilson Chicolet
-----Original Message-----
From: Silveira, Jorge [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > ]
Sent: Wednesday, December 27, 2000 7:01 PM
To: Lista de Discussco Rede Wan
Subject: RES: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> >
Wilson,
Foi o q notei, trabalhando com roteadores Cisco e rede FR!!!! E tb, j�
escutei de v�rias pessoas!!!
Agora, um detalhe. Isto depende da configura��o do roteador. Parametros
como rate enforcement,... QoS como traffic shapping, WFQ,..., dlci
priorization,...solucionam este caso.
PS: Se quiser, podemos discutir mais sobre este assunto. De tb uma olhada em
WFQ(weight fair queued). � bem legal.
Ahh, outra coisa. Ao habilitar o netflow-export no router 7513, o consumo de
CPU pode aumentar em at� 20%, mas o t�pico � 10%, segundo informa��es de
funcion�rio da pr�pria Cisco
[ ]�s
Jorge Francisco de Souza Silveira
Opera��es - Dados & Internet
AT&T Latin America
Rua da Candel�ria, n� 65, Salas 2201 e 2301
Cep 20091-020 - Rio de Janeiro - RJ
Tel.: +55(21) 223-7050 - Fax: (21) 518-8105
[EMAIL PROTECTED]
http://www.attla.com.br <http://www.attla.com.br> < http://www.attla.com.br
<http://www.attla.com.br> > <
http://www.attla.com.br/ <http://www.attla.com.br/> <
http://www.attla.com.br/ <http://www.attla.com.br/> > >
-----Mensagem original-----
De: Wilson Chicolet [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > ]
Enviada em: Quarta-feira, 27 de Dezembro de 2000 15:46
Para: Lista de Discuss�o Rede Wan
Assunto: RE: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> >
Os Roteadores da Cisco n�o se ajustam ao recebimento de BECN/FECN ???
Abra�os,
Wilson Chicolet
-----Original Message-----
From: Silveira, Jorge [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > ]
Sent: Wednesday, December 27, 2000 2:00 PM
To: Lista de Discussco Rede Wan
Subject: RES: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> >
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
Ola Wilson,
Vamos l�,
Frames com o campo DE=1 s�o os primeiros a serem descartados no caso de
congestionamento da rede
Frames com o campo DE=0 s�o, na teoria, sempre entregues ao
destino??!!!!
FECN e BECN servem para indicar congestionamento na rede e para que os
equipamentos negociem, quando assim o fazem, uma menor taxa de transmiss�o.
S� que na pr�tica, roteadores n�o baixam sua taxa de transmiss�o, mesmo
recebendo FECN e BECN ==>a rede/equipamentos switches FR � que fazem o
controle de tr�fego. S� que cada SW tem o sua area de buffer para armazenar
dados(queue), caso haja necessidade.
Agora imagine: 10 links de 2Mbps(cctos FR) conectados ao Switche FR
- n� 1
10 links de 256Mbps(cctos FR) conectados ao
Switche FR - n� 2
sw 1 � conectado ao sw 2, via link de 1Mbps.
E qdo todos estiverem no horario de pico de transmiss�o de dados?? Concorda
que a taxa de transmiss�o vai ser bem mais alta que suportada pelo link de
1Mbps???!!! Agora imagine um monte de frames com bits DE=1 sendo
descartados. Isso vai gerar uma grande quantidade de retransmiss�o de dados,
n�o vai?? Percebe que com isto a rede ficar� cada vez mais complicada para a
entrega de frames??!!! Agora ai vai surpresa....
Nestes momentos os equipamentos podem "decidir" atrav�s de seu algoritmo
pelo descarte de frames com bit DE=0!!! J� vi isso ocorrer. Para maiores
informa��es, pesquise a fundo sobre documentos dos frabricantes e questione
com experts no equipamento.
Tks
Jorge Francisco de Souza Silveira
Opera��es - Dados & Internet
AT&T Latin America
Rua da Candel�ria, n� 65, Salas 2201 e 2301
Cep 20091-020 - Rio de Janeiro - RJ
Tel.: +55(21) 223-7050 - Fax: (21) 518-8105
[EMAIL PROTECTED]
http://www.attla.com.br <http://www.attla.com.br> < http://www.attla.com.br
<http://www.attla.com.br> > < http://www.attla.com.br
<http://www.attla.com.br>
< http://www.attla.com.br <http://www.attla.com.br> > > <
http://www.attla.com.br/ <http://www.attla.com.br/> <
http://www.attla.com.br/ <http://www.attla.com.br/> > <
http://www.attla.com.br/ <http://www.attla.com.br/> <
http://www.attla.com.br/ <http://www.attla.com.br/> > > >
-----Mensagem original-----
De: Wilson Chicolet [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> >
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > > ]
Enviada em: Sexta-feira, 22 de Dezembro de 2000 12:22
Para: Lista de Discuss�o Rede Wan
Assunto: RE: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> >
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
Jorge,
Me desculpe, mas eu n�o entendi o seu E-mail anterior. Voc� pode me
esclarecer ???
Obrigado,
Wilson Chicolet
-----Original Message-----
From: Silveira, Jorge [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > ]
Sent: Thursday, December 21, 2000 2:14 PM
To: Lista de Discussco Rede Wan
Subject: RES: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> >
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
>
Wilson,
S� para complementar, observe o que disse quanto a descarte de frames na
rede da provedora de acesso. CIR tb pode ser descartado!!
Tks
Jorge Francisco de Souza Silveira
Opera��es - Dados & Internet
AT&T Latin America
Rua da Candel�ria, n� 65, Salas 2201 e 2301
Cep 20091-020 - Rio de Janeiro - RJ
Tel.: +55(21) 223-7050 - Fax: (21) 518-8105
[EMAIL PROTECTED]
http://www.attla.com.br <http://www.attla.com.br> < http://www.attla.com.br
<http://www.attla.com.br> > < http://www.attla.com.br
<http://www.attla.com.br>
< http://www.attla.com.br <http://www.attla.com.br> > > <
http://www.attla.com.br <http://www.attla.com.br>
< http://www.attla.com.br <http://www.attla.com.br> >
< http://www.attla.com.br <http://www.attla.com.br> <
http://www.attla.com.br <http://www.attla.com.br> > > > <
http://www.attla.com.br/ <http://www.attla.com.br/> <
http://www.attla.com.br/ <http://www.attla.com.br/> > <
http://www.attla.com.br/ <http://www.attla.com.br/> <
http://www.attla.com.br/ <http://www.attla.com.br/> > > <
http://www.attla.com.br/ <http://www.attla.com.br/> <
http://www.attla.com.br/ <http://www.attla.com.br/> > <
http://www.attla.com.br/ <http://www.attla.com.br/> <
http://www.attla.com.br/ <http://www.attla.com.br/> > > > >
-----Mensagem original-----
De: Wilson Chicolet [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> >
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > >
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> >
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > > > ]
Enviada em: Quarta-feira, 20 de Dezembro de 2000 17:16
Para: Lista de Discuss�o Rede Wan
Assunto: RE: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> >
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
>
Valdinei,
Realmente voc� precisa especificar o CIR, sen�o o Cisco vai assumir o
default (por omiss�o) que � 56Kbps.
Ex.: primeiro o comando map-class frame-relay cir e depois frame-relay cir
32000 (para o circuito de 64Kbps) e frame-relay cir 128000 (para o circuito
de 256Kbps), normalmente o CIR contratado � o mesmo na recep��o (in) e na
transmiss�o (out), por isso voc� pode utilizar o exemplo acima.
Veja o exemplo abaixo, tirado do site da Cisco:
frame-relay cir
To specify the incoming or outgoing committed information rate (CIR) for a
Frame Relay virtual circuit, use the frame-relay cir map-class configuration
command. To reset the CIR to the default, use the no form of this command.
frame-relay cir {in | out} bps
no frame-relay cir {in | out} bps
Syntax Description in | out
Incoming or outgoing.
bps
CIR in bits per second.
Defaults
56000 bits per second
Outra coisa, n�o deixe de configurar o Traffic Shaping, pois com ele voc�
evitar� a possibilidade de descarte de pacotes.
Ex.: Entre na interface serial a ser utilizada e introduza o comando
frame-relay traffic-shaping.
Veja o exemplo abaixo tirado do site da Cisco:
Traffic shaping (Frame Relay or generic) is only supported in the fast
switching and process switching paths. Thus, you must ensure other switching
methods (optimum, NetFlow, and so on) are disabled on all other interfaces
that will be sending traffic to this serial interface.
If traffic shaping is enabled, the router checks to see if there is credit
built up so it can transmit the packet. If there is no credit, the router
queues the packet to whatever queue has been set up for that virtual circuit
(VC), such as FIFO, CQ, or PQ (FIFO is the default). If there is credit
available, the router sends the packet to the output interface and deducts
the packet size from the available credit. The router also starts the "xmit"
process on the interface. Also of note is the fact that PQ/CQ queue sizes
can be adjusted via normal commands, while the FIFO shaping queue on the VC
defaults to 40 and cannot be changed. If you have to change the queue depth
on FIFO, enable either custom queueing or priority queueing and put all
traffic in one queue.
After every time interval (measured in milliseconds which usually equates to
Tc), the router starts a loop which does the following:
Adds the byte increment (normally Bc/8) to the available credit. It checks
to see if there is credit available to send a packet from this VC. If so,
the process dequeues a packet.
Checks to see what the "qcount" (number of packets currently in interface
output queue) is and saves this value.
Sends the packet to the output interface and starts the transmit process. It
also charges the VC for this packet.
Checks the value of "qcount" that was obtained earlier to see if it's
greater than 0. If so, it breaks out of the loop. This output queue check is
done in order to prevent one VC from overrunning the interface output queue
and causing important packets to be discarded.
If the output queue count is zero, the router continues sending more packets
until either there is no data to send, the VC has used up all of its credit,
or the output queue count becomes greater than zero.
Backward Explicit Congestion Notification (BECN) Response
If the router receives any BECNs during the current time interval, it
decreases the transmit rate by 25%. The rate will continue to drop with each
BECN (limit one drop per time interval) until the traffic rate gets to the
minimum acceptable incoming or outgoing committed information rate (MINCIR),
where it stops.
Once the traffic rate has decreased, it takes 16 time intervals of receiving
no BECNs to start to increase traffic again. Traffic increases (Be+Bc)/16,
or more accurately, the byte limit that shows up in show traffic and show
frame-relay pvc x divided by 16. Thus, it takes much longer to get back to
committed information rate (CIR) than it did to drop to the MINCIR (similar
to slow start in TCP/IP). One way of making this length of time much shorter
would be to set "Be" 7 times the value of "Bc," which would ensure it gets
back to CIR immediately after going through 16 time intervals without a
BECN. Also of note is that this increase only occurs when traffic shaping is
active. If traffic shaping is not active, the transmit increment stays the
same even though BECNs are not being received.
Some terms related to BECN response are explained below:
Tc
The Bc/Cir time interval (the internalized version of Tc where the time
interval can't exceed 125ms).
CIR
The average rate you want to send out. (This is generally not the same as
the CIR you get from your provider unless you aren't allowed to send above
CIR.) This is measured in bits/second.
Bc
The amount of data to send per each Tc interval. This is measured in bits.
(This is also internalized and the real amount of data sent per interval is
expressed in bytes by the "increment" variable.)
Be
The amount of excess data allowed to be sent during first interval once
credit is built up. Measured in bits.
Mincir
The minimum amount of data to be sent during periods of congestion. This
defaults to half of CIR.
Interval
Bc/CIR, with the maximum size being 125ms.
byte increment
Bc/8. Must be greater than 125. Upper side has no bound or limitation except
if interval is locked at 125ms.
limit
Byte increment + Be/8 (measured in bytes).
Example 1
This example includes a Frame Relay link with the following parameters:
Physical port speed of 64KB
CIR = 16KB (This refers to the CIR your provider has guaranteed in their
network.)
The provider has specified that you can send data on the PVC up to port
speed as long as there is no congestion in their network, but that when
there is congestion they will guarantee only CIR on the PVC.
In this case, configure the following on the router:
encap frame-relay
ip address 10.10.10.1 255.255.255.0
frame-relay traffic-shaping
frame-relay map ip 10.10.10.2 200 broadcast
frame-relay interface-dlci 200
class 64KB
map-class frame-relay 64KB
frame-relay cir 64000 <--- This is rate you want to normally send at
when there is no congestion.
frame-relay bc 8000 <--- This is amount you will send per
interval. A good rule of thumb is to
make it 1/8 CIR.
frame-relay be 0 <--- This is extra amount to send in first
interval. In this case you are already
sending at port speed so this should be
0.
frame-relay mincir 16000 <--- This is what you will slow down to during
congestion. This should be set to
your true CIR that your provider has
guaranteed you when there is congestion
in their network.
Note: BECN Response (decreasing its transmit rate when receiving BECNs) is
enabled by default in Cisco IOS 11.2.
In traffic shaping, Tc= Bc/CIR, where Tc is the measurement interval. This
value should be no larger than 1/8 second for effective shaping to take
affect.
So in the above example, Tc = 8K/64K = 1/8 second.
This is what you would see transmitted in 1/8 second intervals:
8000(Bc+Be), 8000(Bc), 8000, 8000, 8000, 8000, 8000, 8000
This equals 64000bits/second.
If the port speed was actually 128KB but the Be = 64000 instead, then this
is what you would see:
72000, 8000, 8000, 8000 ....
The router would keep sending at Bc(8000) until there was an idle interval
or only a partially used interval and the credit built up again. The maximum
credit the router can build up is Be. The configuration is shown below:
interface Serial5/1:1
ip address 10.10.10.1 255.255.255.0
encapsulation frame-relay
no ip mroute-cache
frame-relay traffic-shaping
frame-relay interface-dlci 50
class test
map-class frame-relay test
frame-relay adaptive-shaping becn
frame-relay cir 64000
frame-relay bc 8000
frame-relay be 72000
frame-relay mincir 16000
Here are some show commands that you can use to see these numbers:
wan-7507a#show frame-relay pvc 50
PVC Statistics for interface Serial5/1:1 (Frame Relay DTE)
DLCI = 50, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE =
Serial5/1:1
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
Shaping adapts to BECN
pvc create time 23:34:33, last time pvc status changed 23:34:33
cir 64000 bc 8000 be 72000 limit 10000 interval 125
mincir 16000 byte increment 1000 BECN response yes
pkts 0 bytes 0 pkts delayed 0 bytes delayed 0
shaping inactive
Serial5/1:1 dlci 50 is first come first serve default queueing
Output queue 0/40, 0 drop, 0 dequeued
wan-7507a#show traffic-shape
Access Target Byte Sustain Excess Interval Increment Adapt
I/F List Rate Limit bits/int bits/int (ms) (bytes) Active
Se5/1:1 64000 10000 8000 72000 125 1000 BECN
wan-7507a#show traffic-shape statistics
Access Queue Packets Bytes Packets Bytes Shaping
I/F List Depth Delayed Delayed Active
Se5/1:1 0 0 0 0 0 no
wan-7507a#
Example 2
In this example, router Frame Relay 45 (FR45) is a hub router and Frame
Relay 3 (FR3) is a spoke router.
FR45 Router Configuration
Current configuration:
!
version 11.2
!
hostname FR45
!
!
interface Ethernet0
ip address 192.150.42.61 255.255.255.248
media-type 10BaseT
!
!
interface Serial0
no ip address
encapsulation frame-relay
no fair-queue
frame-relay traffic-shaping
<--- Enable traffic shaping on
interface.
!
interface Serial0.1 point-to-point
ip address 171.68.157.113 255.255.255.240
ipx network AB449D80
frame-relay class 32cir
<--- Here, the map class defined as
follows is assigned
to subinterface.
frame-relay interface-dlci 101 broadcast
!
interface Serial0.2 point-to-point
ip address 171.68.157.129 255.255.255.240
frame-relay class 16cir
<--- Here, the map class defined as
follows is assigned
to subinterface.
frame-relay interface-dlci 102 broadcast
!
interface Serial0.3 point-to-point
ip address 171.68.157.145 255.255.255.240
frame-relay class bc64
<--- Here, the map class defined as
follows is assigned
to subinterface.
frame-relay interface-dlci 103 broadcast
!
!
router Enhanced IGRP 44
network 171.68.0.0
!
ip route 171.69.1.129 255.255.255.255 192.150.42.62
!
map-class frame-relay 32cir
frame-relay traffic-rate 32000 64000
<--- Here, the average and peak rates
are set to the
VCs CIR, and Be.
frame-relay custom-queue-list 1
<--- Here, a custom queue list is also
assigned to this
map class.
!
map-class frame-relay 16cir
frame-relay traffic-rate 16000 64000
<--- Here, the average and peak rates
are set to the
VCs CIR, and Be.
!
map-class frame-relay bc64
frame-relay cir in 32000
<--- Here, specific control of
parameters is possible on
a bidirectional basis.
frame-relay cir out 32000
frame-relay bc in 32000
frame-relay bc out 64000
frame-relay be in 64000
frame-relay be out 64000
!
queue-list 1 protocol ip 1
queue-list 1 protocol ipx 2
queue-list 1 queue 1 byte-count 4200
queue-list 1 queue 2 byte-count 1400
!
!
end
FR3 Router Configuration
Current configuration:
!
version 11.2
!
hostname FR3
!
enable password cisco
!
ipx routing 0000.0c18.d70c
!
interface Ethernet0
ip address 198.19.1.1 255.255.255.0
ip helper-address 171.68.159.82
ipx network C6130301
!
!
interface Serial0
ip address 171.68.157.146 255.255.255.240
encapsulation frame-relay
ipx network AB449D90
frame-relay traffic-shaping
frame-relay class 32cir
<--- Here, the map class defined as
follows is assigned
to interface.
!
router Enhanced IGRP 44
network 171.68.0.0
!
!
no ip classless
ip route 171.69.1.129 255.255.255.255 192.150.42.161
!
map-class frame-relay 32cir
frame-relay traffic-rate 32000 64000
<--- Here, the average and peak rates
match those in
the hub router.
frame-relay custom-queue-list 1
<--- Here, the custom queue list
matches that in the
hub router.
!
queue-list 1 protocol ip 1
queue-list 1 protocol ipx 2
queue-list 1 queue 1 byte-count 4200
queue-list 1 queue 2 byte-count 1400
!
!
end
Bom estudo e boa sorte.
Abra�os,
Wilson Chicolet
A PROP�SITO, UM NATAL COM MUITA PAZ PARA TODOS OS PARTICIPANTES DA LISTA DE
DISCUSS�O.
-----Original Message-----
From: Valdinei Castelan [ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > >
< mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> <
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > ]
Sent: Tuesday, December 19, 2000 7:11 PM
To: Lista de Discussco Rede Wan
Subject: [redewan] Cisco, Frame relay e config. CIR
Lista de Discuss�o Rede Wan - http://www.networkdesigners.com.br
<http://www.networkdesigners.com.br>
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> >
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
>
< http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
<
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> <
http://www.networkdesigners.com.br <http://www.networkdesigners.com.br> > >
>
>
Caros amigos,
Tenho o seguinte caso:
Um link frame-relay 256 com cir 128, interligando pontos b, c, d, etc de 64
com cir 32.
N�o configurei nada especificamente quanto a CIR, etc, entendendo que a
utiliza��o de banda se controlava automaticamente, mas me parece que n�o �
assim. Como devo configurar o router Cisco 2501 e 1601?
Grato,
Valdinei Castelan
Diretor de Tecnologia
CNE - Certified Novell Engineer
MCP - Microsoft Certified Professional
[EMAIL PROTECTED]
DPI Desenv. de Projetos em Inform�tica
www.dpinet.com.br // 0 xx 15 227-8104
Sorocaba - S�o Paulo - Brazil
______________________________________________________________________
_____
______________________________________________________________________
_____
______________________________________________________________________
_____
______________________________________________________________________
_____
______________________________________________________________________
_____
|
