> Imagine my surprise when I wanted to enable RED on a couple of
> saturated T1 links, only to discover that it's not supported on
> the "S" (Service Provider) releases! Can this be true? It seems
> like the Service Providers are the customers who would be able to
> make the most of RED...after all, we're running only IP.
>
> Cisco TAC says we need 12.0T (yuk), 12.1 mainline, 12.1E, or
> 12.1T. What gives? Isn't anyone using this? It sure sounds
> like a great idea. Of course, the big problem is that only
> TCP responds to drops.
Strange, we seem to have it here:
Cisco Internetwork Operating System Software
IOS (tm) RSP Software (RSP-JSV-M), Version 12.0(11.3)S, EARLY DEPLOYMENT MAINTENANCE INTERIM SOFTWARE
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Wed 14-Jun-00 22:24 by htseng
...
System image file is "slot1:rsp-jsv-mz.120-11.3.S"
POS5/0/0 is up, line protocol is up
Hardware is cyBus Packet over Sonet
Internet address is a.b.c.d
MTU 4470 bytes, BW 155000 Kbit, DLY 100 usec, rely 255/255, load 19/255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Scramble enabled
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Packet Drop strategy: VIP-based random early detection (DWRED)
Output queue 0/40, 368680 drops; input queue 0/75, 10534 drops
5 minute input rate 25227000 bits/sec, 4830 packets/sec
5 minute output rate 11799000 bits/sec, 2498 packets/sec
Steinar Haug, Nethelp consulting, sthaug@nethelp.no
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:16 EDT