Hello I agree with the others, if you have to apply QoS for an ADSL link
(upstream traffic only) you must enforce some sort of queueing / shaping on
a lower layer. The ATM vc that your connection uses is the just right place
for this.
Just that when I tried something similar I could only make CBWF
The problem you have is that there's no outbound queue forming on the Dialer
interface (PPPoE is too fast, as it goes over outside Ethernet).
http://blog.ioshints.info/2009/06/adsl-qos-basics.html
You have to apply shaping to force a queue to form. The shaping has to be
configured on the physical
Sorry Guys,
figured it out by myself - "vbr-nrt" is the magic word:
interface ATM0
no ip address
no atm ilmi-keepalive
!
interface ATM0.1 point-to-point
no ip redirects
no ip unreachables
no ip proxy-arp
pvc 1/32
vbr-nrt 923 923
tx-ring-limit 2
encapsulation aal5snap
service-policy
Hi,
does anybody know if the Cisco 876 is supporting LLQ on Dialer
Interfaces (PPPoE over ATM)?
The Packets are classified correctly by NBAR:
Class-map: ef (match-all)
21 packets, 5124 bytes
5 minute offered rate 1000 bps, drop rate 0 bps
Match: dscp ef (46)
Prio
You have to do this under the dialer int. I've got a similar config
but on 871. In any case, I moved away from 1700 platform due to a
similar issue (but I don't remember the specifics, sorry.)
What version are you running now?
--William McCall
On Tue, Jul 7, 2009 at 4:20 PM, Clue Store wrote:
>
Awesome. Big thanks to Thomas and Siva for the clue bits. They are greatly
appreciated!!
--
Clue
On Tue, Jul 7, 2009 at 4:59 PM, Siva Valliappan wrote:
> correct. vbr-nrt only affects the output not the input.
>
>
> regards
> .siva
>
> On Tue, 7 Jul 2009, Clue Store wrote:
>
> Hi Siva,
>>
>> Y
correct. vbr-nrt only affects the output not the input.
regards
.siva
On Tue, 7 Jul 2009, Clue Store wrote:
Hi Siva,
Your suggestions seem to have to have worked. Just so that I understand, the
vbr-nrt shaping is just for the outbound cells and does not affect inbound
traffic correct?? This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You don't need the subif - use the phy interface.
Brgds
TS
- -Ursprüngliche Nachricht-
Von: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] Im Auftrag von Clue Store
Gesendet: Dienstag, 7. Juli 2009 23:21
An: S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Clue,
yes your right. applying the sp to the dialer interface is a bad idea (see IP's
ioshints blog) - also IMHO to the virt template (never tried it). To support
LLQ and CBWFQ on DSL Interfaces you have to:
- change the vc to vbr-nrt
Hi Siva,
Your suggestions seem to have to have worked. Just so that I understand, the
vbr-nrt shaping is just for the outbound cells and does not affect inbound
traffic correct?? This is a 3m/384k and I do not want to affect their
inbound. I could only reserve 288k in my policy (which is fine sinc
On Jul 8, 2009, at 2:49 AM, Drew Weaver wrote:
I've seen the Cisco TTL Expiry attack documentation etc, are there
any good generalized guidelines Cisco published or not?
CoPP is very situationally specific. Suggest you use NetFlow,
classification ACL, etc. to build your policy, then do a
what does the log messages say? a show log should tell you why it
didn't accept the commands.
On Tue, 7 Jul 2009, Clue Store wrote:
It took the command under the pvc section, but after a "sho run" the config
did not show up. Nor when I did a "show policy-map interface a0.1" did
anything show u
it's been many years since i worked in this area, so you will need to
bear with me.
couple of things to check. can you do a "show log" and is there any
other messages that were generated when you tried to configure the
service policy on the ATM interface?
do you have a "vbr-nrt " definition und
It took the command under the pvc section, but after a "sho run" the config
did not show up. Nor when I did a "show policy-map interface a0.1" did
anything show up.
I've looked through several docs on the cisco site, but did not come up with
anything that seem'd to work.
Will try to upgrade the I
My apologies, I did not apply it under the PVC section. It took that just
fine and would make sense that the policy is applied to the VC itself. I
will test and see how well this works.
Thanks
On Tue, Jul 7, 2009 at 4:06 PM, Siva Valliappan wrote:
> IIRC you need to apply it on the ATM interfac
On A0.1.
config-subif)#service-policy output Voice
CBWFQ : Not supported on subinterfaces
On A0
(config-if)#service-policy output Voice
CBWFQ : Not supported on this interface
It would seem out old ways of QoS have changed ;)
On Tue, Jul 7, 2009 at 4:06 PM, Siva Valliappan wrote:
> IIRC
ndle. Will you be running
dynamic routingprotocols? What protocols will you use for remote access etc?
More info is needed if we are going to try to answer your question.
/Daniel
__ Information from ESET NOD32 Antivirus, version of virus signature
database 4222 (20090707) __
The m
IIRC you need to apply it on the ATM interface
e.g.
Interface ATM0.1 point-to-point
.
.
pvc 1/100
service-policy output Voice
regards
.siva
On Tue, 7 Jul 2009, Clue Store wrote:
Hi All,
I am having a hard time trying to figure how to apply a QoS policy on this
router. I have applied a f
Hi All,
I am having a hard time trying to figure how to apply a QoS policy on this
router. I have applied a few typical service-policies on the dialer
interfaces, but a "show policy interface di0" shows packets being matched
but nothing being dropped and the link is saturated. I believe the polic
can handle. Will you be running
dynamic routingprotocols? What protocols will you use for remote access etc?
More info is needed if we are going to try to answer your question.
/Daniel
__ Information from ESET NOD32 Antivirus, version of virus signature
database 4222 (20090707) _
Hi all,
Does anyone have any baseline CoPP policies to put in place on a switch
where you can't really anticipate the kind of traffic that will be coming into
it but you need the IP INPUT processes, etc to stay at some level of control?
I've seen the Cisco TTL Expiry attack doc
Hi all,
I am trying to establish a bridged solution for 5 locations that are served
via ADSL non-authenticated connections. These ADSL connections are
delivered to us via a wholesale provider and we do not have the ability to
control the network or implement changes.
The network topology of the
Ivan,
>
> BTW, even the more "traditional" fast convergence techniques (internal BGP
> fast fallover) might be too aggressive and do more harm than good.
>
Could you elaborate little more on that?
I thought it would be a good idea (e.g. neighbor X fall-over
route-map) to drop BGP session with a n
Hello all
I am experimenting with a 7200 router playing the role of DHCP server
for xDSL subscribers.
In this simple setup the 7200 is the first L3 node for the xDSL
subscribers. Apart from playing
the role of the default gateway, the 7200 using its local DHCP server
also handles the address
alloc
24 matches
Mail list logo