[c-nsp] 6500 SUP720 High Latency and Jitter issues

[Jared Mauch]

On Wed, May 25, 2005 at 03:30:57PM -0700, Ian Cox wrote:
> At 11:26 PM 5/25/2005 +0200, Gert Doering wrote:
> >Hi,
> >
> >On Wed, May 25, 2005 at 12:27:26PM -0700, Tim Stevenson wrote:
> >> Ah - you can't use the same IP (same loopback) for all your tunnels, you
> >> have to use unqiue IPs to terminate the tunnels.
> >
> >I would find it enormously useful if IOS issued a warning if you
> >configure something that will be "perfectly fine" on other platforms,
> >but will drop the box to software switching on the Sup720...
> 
> When configuring the tunnel interface on Sup720 it tells you if it 
> will be hardware or software switched.
> 
> 7609-1(config)#int tunnel 1
> 7609-1(config-if)#tunnel key 0
> %Warning: Feature not supported in hardware. Tunnel1 packets will be
> software switched
> 7609-1(config-if)#no tunnel key 0
> Tunnel1 packets will now be hardware switched.

	Great, more random crap that will break automated configuration
tools.

	Does the boot time parser also log this crap like the /31 logging
that goes on if you use it on a ethernet based media?  Does ciscos
testing/regression facility even test this stuff?  It's be nice if
booting IOS would not log excess junk.. eg:

*Mar  1 00:00:04.013: %REGISTRY-3-STUB_CHK_OVERWRITE: Attempt made to overwrite a set stub function in reg_add_dsx1_busyout_card_xcc_timeslots.
-Process= "Init", ipl= 3, pid= 3
-Traceback= 8044FEB4 801AC874 80452D5C 80452DFC 8036CD18 8036CF18 8045A45C 8045DB08

	If you can't fix your boot-time bugs, what is being done
to seriously address real issues?

	Then, the system decides to syslog in a different
format too, eg:

*Feb 28 19:00:16.602 EST: %AAAA-4-BADMETHNAME: Bad authentication method-list name "local" (this is only a warning)

	a few seconds later once it actually uses the configured
logging specs..

	- jared

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.