HDTenEightyP/NetNews huggingface dataset:
From: koelman@cuby.stc.nl (Ton Koelman)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: PPP question
Date: 16 Oct 92 12:29:33 GMT
Reply-To: koelman@stc.nato.int
Organization: SHAPE Technical Centre, NL

In article <fontaine-071092160947@130.104.58.7> fontaine@sri.ucl.ac.be  
(Alain Fontaine) writes:
> At the risk of offending the audience of this list, I must first state  
that
> we don't have any cisco machines ; our (IP) network is build with  
routers
> from
> another vendor. But I must now connect our network to another site that
> uses
> cisco's. PPP, of course. I have heard that the cisco's PPP  
implementation
> does not support the LQM stuff. OK, I know how to disable it on my  
routers.
   
We're dealing here with a Wellfleet that exhibits this problem.
How do you turn of the LQM stuff on a Wellfleet?

thanks
                          
--
Ton Koelman   e-mail: koelman@stc.nato.int (NeXT Mail Welcome!)
SHAPE Technical Centre, P.O. Box 174, 2501 CD  The Hague
The Netherlands  (voice: 31-70-3142429, fax: 31-70-3142111)
Newsgroups: comp.dcom.sys.cisco
From: rh0083b@medtronic.COM (Roger-Hunen)
Subject: Re: Cisco Bridging
Organization: Medtronic, Inc.
Date: Tue, 13 Oct 1992 07:10:55 GMT

In article <1992Oct12.081211.5814@walter.cray.com> hens@snipe.cray.com (Tom Stephens) writes:
>I have read through the doc on bridging with a Cisco.  It seems that Cisco's
>can either act as a bridge *OR* a router not both at the same time.  All I
>want to do is bridge two ethernets together and keep routing IP as I am now.
>It seems like a fairly simple request.  Has anyone else had luck with this,
>or is this not possible with a Cisco router?

With Cisco routers you can route IP and bridge others, no problem. You just
cannot route *and* bridge the same protocol.

Regards,
-Roger
From: dumic@cc.swarthmore.edu (Mark J. Dumic)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: 9.0 software queue flush failure?
Date: 8 Oct 92 19:13:05 GMT
Followup-To: comp.dcom.sys.cisco
Organization: Swarthmore College

In article <mark.718300525@wugate.wustl.edu>, mark@wupost.wustl.edu (Mark
Pohlman) wrote:
> 
> Has anyone noticed a problem with queues filling up on its interfaces and not
> flushing its queues properly on 9.0. We've had interfaces on our ciscos showing 
> 76/75 input queue and hanging the interface.
> 
> Only able to clear by RELOAD.

I been having the same problem but only when I cut/paste Cisco
configuration commands into a telnet window.  Supposedly, this was a
problem with 9.0(1) that was fixed in 9.0(2) according to Cisco.  I'm
installing the 9.0(2) EPROMS tomorrow morning so I'll soon know.  I'll post
the results.
Newsgroups: comp.dcom.sys.cisco
From: tdawson@iphase.com (Tim Dawson)
Subject: Re: Performance-Problems with IGS
Organization: Interphase Corporation, Dallas Texas
Date: Thu, 15 Oct 1992 16:21:10 GMT

dewey@centerline.com (Devan F. Dewey) writes:

>In article <schulte.718616369@nagoya>, schulte@nagoya.sni.de (Schulte)
>wrote:
>> 
>> 
>> Hi there,
>> I'm new with cisco's and I found some performance-problem, I get only
>> 1 kByte over a 64kbit x.25-line. Maybe I made something wrong I my config, 
>> because having a direct-line with the same speed and one IGS with X25-DCE 
>> and the other IGS as X25-DTE I get 5.8kByte per second.
>> This is my config: (the other cisco has the same with changed address)
>> 
>> 2 IGS 1MByte memory connected over a 64kByte Packet-Switch
>> with following bootfile-contents:


>I have configured my serial interface like this:

>interface Serial 0
>encapsulation X25
>bandwidth 56   <<<<<<<<<<<<<<<<<
>x25 win 7
>x25 wout 7
>x25 hic 64
>x25 htc 64
>x25 hoc 64
>x25 th 1
>x25 nvc 8

>The line I've marked is because we have a 56K line to our modem. If you
>have a 64K line, shouldn't you have a line that looks like this:

>bandwidth 64

>????????

>Hope this helps,


>Devan

Actually, this will not help.  The bandwidth command on a cisco sets the 
administrative bandwidth only - not the actual port speed.  What this is used
for is determining route metrics of things like IGRP which take line speed into
account, and cannot otherwise determine the speed the line is running.  Since
these ports are synchronous, they will talk to the modem (if it sources clock,
which is typical) at the modems speed.  Hence if you had a high speed route
but wanted it to be a low route priority, or override a hop count to go to
a cheaper but longer route, one way is to diddle the bandwidth in the config.

(This can also make you grow prematurely grey when you have a 56K line on
a high speed serial (defaults to bandwidth 1.54Mbit) take all your traffic 
although you have another 56 on a low speed serial (defaults bandwidth to 56K)
with a 3 hop shorted route, and the long route gets the traffic!  Very useful,
but a bit confusing, would be the bottom line here . . . . 

-- 
================================================================================
Tim Dawson (tdawson@iphase.com)     Unix Systems Admin. / Software Group Leader
Interphase Corporation - MIS        Bellnet: (214)-919-9303, FAX: (214)919-9200
13800 Senlac, Dallas, Texas, 75234  ---< This space for rent cheap . . . . >---
From: ce@raistlin.udev.cdc.com (CDC Customer Engineering)
Newsgroups: comp.dcom.lans.ethernet
Subject: High collision rates on ethernet
Date: 13 Oct 92 20:14:11 GMT
Reply-To: ce@raistlin.udev.cdc.com
Organization: Control Data.

Keywords:collisions 


Need info.

We are experiencing a very high number of collisions with devices using SEEQ chipsets.
The type of chips are  NQ8003 and NQ8020.  The test case we used was to FTP a large file across a single piece of ethernet (thin) between 2 workstations.  The only other devices on the trunk were a sniffer and a HP 4972.  While the data transfer was taking place, we consistantly see collisions in excess of 20 to 30 percent.  We have tried all types of media, transceivers, fannouts, cables, etc.  The results are always the same

On the plus side, we see network throughput at about a 8 megabit rate with these devices.  The problems result when we try to utilize these devices on a network with workstations using other mfg's chipsets.

One other negative we suspect (no proof yet) is that older fannouts, repeaters, bridges, and hubs are unable to keep up with the data xfer rate of these chips.

In general, we are able to obtain high throughput rates from devices with this chipset, but all other devices on the network appear to suffer dramatic slowdowns.  We are also
having a difficult time explaining to users why their network has gone from a 1 to 2
percent collision rate to a 20 percent collision rate.

Any thoughts, ideas ??

Ron Lewis
Network Support
From: mark%fdc@Arizona.edu (Mark R. Toth)
Newsgroups: comp.dcom.lans.ethernet
Subject: Any info on `ACCTON' 16-bit ethernet cards?
Keywords: accton,ethernet card
Date: 9 Oct 92 23:44:12 GMT
Organization: Facilities Design & Construction, Univ of Az, Tucson, AZ, USA

Howdy,

   I've got a sales type pushing a 16-bit PC/AT bus ethernet card for
about $30 less than what I can get for an EtherLink II.  Has anyone
worked with these and could say what kind of failure rate or configuration
problems they've had.  Expected software to be run on these would be
NCSA's Telnet, Novell 3.11, FTP's TC/IP, SUN PC-NSF and/or DEC Patchworks
depending upon which college would use these.  Most interest would likely
be in the 10baseT and then 10base2 versions with a few areas still using
10base5 media.

Thanks
8{)
.............................................................................
                                                            ##   
Mark R. Toth                                      |        ####
University Of Arizona                           | |         ##     
Facilities Design & Construction                | | |             
Physical Resources Bldg #49, Rm 140A            `-| |             
Tucson, Arizona, USA 85721                        |-'            
(602) 621-5281 fax:621-5668          _____________|_______________________
Internet: mark%fdc@arizona.edu         {Not a spokesperson/My views only}
.............................................................................
  Anybody seen my submarine?  I tied it up over there by the cactus...
Newsgroups: comp.dcom.lans.ethernet
From: barr@tramp.Colorado.EDU (BARR DOUG)
Subject: Dividing up a subnet into groups
Organization: University of Colorado, Boulder
Date: Wed, 7 Oct 1992 17:11:43 GMT

Because of high traffic volumes we want to divide up a subnet into 
different workgroups. We may do this with a bridge or a router.
However, my first task is to take some statistics on who is communicating
with whom. We have about 150 devices on this net. Does anyone know of a 
good methodical way of dividing up this group. We obviously want to
put workstations that have high amounts of traffic between them on the 
same side of the bridge or router. I have a Sniffer and an old HP network
analyzer.

Newsgroups: comp.dcom.lans.ethernet
From: eletanjm@nuscc.nus.sg (Tan Jin Meng)
Subject: 3c503 specs anyone? 
Organization: National University of Singapore
Date: Wed, 7 Oct 1992 12:47:54 GMT

I am writing a driver for the 3COM etherlink II (aka 3C503) card. I have
some code fragments which are badly commented and furthermore do not
describe the adapter architecture at all (ie a register level
description). The lack of a register level description makes me
especially wary of tackling the project.

Can some kind soul help me  out and  either tell me how to get hold of
or give me the specs for the card.

Thanks a million!

jin meng

Newsgroups: comp.dcom.lans.ethernet
From: khindria@maccs.dcss.mcmaster.ca (Vivek Khindria (CSU))
Subject: Re: Jumper settings of 3c501 network card?
Organization: McMaster University, Hamilton, Ontario, Canada.
Date: Thu, 8 Oct 1992 18:03:21 GMT

In article <1992Oct6.142314.49737@ccvax.ucd.ie> bradshaw@ccvax.ucd.ie writes:
>Does anyone out there know the harware settings for the 3c501
>ethernet card? What do each of the jumpers represent?
>All replies appreciated....Thanks in advance....
>My E-Mail addresses follow:-
>
>CBRADH89@IRLEARN.UCD.IE
>BRADSHAW@CCVAX.UCD.IE


   I know of at least two versions of the 3c501.  Both are labeled for most
 of the settings.  The largest jumper selects the type of ethernet DIX for thick and AUI for thin.
    There is a jumper for interrupt (2-7) and the DMA channels (1-3).
    The I/O address for 100h is (d=down,u=up)  DDDDUU
    The memory setting for 300h is DDUUDUUU.

    A typical setting may be AUI,Int 5, I/O 100h, Memory 300h, DMA 1/1

  Hope this helps.

  Vivek Khindria
  McMaster University, Hamilton, Ontario, Canada
From: laut@alien.gici.com (Bill Laut)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Subnetting question...
Date: 11 Oct 92 21:08:07 GMT
Organization: Gull Island Consultants, Inc.

In article <1992Oct9.180714.25050@sun1x.actc.res.utc.com>, dowd@sun1x.actc.res.utc.com (Kevin Dowd) writes:
> Does anyone have words of advice about breaking a class B network
> into different sized subnets?  I know it's not provided for in 
> rfc950, but I wonder if people do it anyway, and if so, what are 
> the dangers?
> 
> Thanks in advance.  
> 
> -Kevin

We tried doing this at one client site.  Technically, you can do it.  In
fact, you can even create arbitrary subnet masks of non-contiguous bits,
although that can make debugging a somewhat novel experience (:-).

Back in the early days of routers, when memory was expensive and routers
had limited switching speed, the reason for varying the size of the subnet
mask was to decrease the number of entries in your routing table.  In other
words, if your network resembled a tree, you could decrease the number of
subnet bits as you got closer to the trunk, and thus the routers that made
up the trunk itself wouldn't have to traverse a big routing table to 
figure out where to route the datagram.

Nowadays, routers are fast enough and have enough memory that this practice
generally is discouraged.  Of course, if/when the Internet goes to 64 or
more bits, anything goes.  You, too, can dynamically map 4 billion 
networks via OSPF (:-).  Ahh, for the days of Default routes....


-- 
Bill Laut			Internet:  laut@alien.gici.com
Gull Island Consultants, Inc.	Phone:     (616) 780-3321
P.O. Box 627
Muskegon, MI  49440		>> "Usual disclaimers, apply within" <<
From: dey@unix1.cs.umass.edu (Jayanta K. Dey)
Newsgroups: comp.dcom.lans.ethernet
Subject: Start-up delay in Ethernet repeators.
Date: 8 Oct 92 14:52:26 GMT
Reply-To: dey@unix1.cs.umass.edu (Jayanta K. Dey)
Organization: University of Massachusetts, Amherst



I am posting this question for a friend of mine.

Are there any adverse system effects if a Ethernet repeator does not meet
the AUI to AUI start-up delay IEEE specifications. Will it lead to configuration 
limitations. Can i still have 4 AUI hops?

Please send your replies to 


ganesan@thales.math.umass.edu

Thanks
An engineer is a person who passes as an exciting technical expert on
the basis of being able to turn out with prolific fortitude, infinite
strings of incomprehensive estimates calculated with microscopic
precision from vague assumptions and debatable figures taken from
Newsgroups: comp.dcom.lans.ethernet
From: vishwas@cse.iitb.ernet.in (Vishwas Joglekar)
Subject: Ethernet / Drop cable
Organization: Department of Computer Science,IIT, Bombay
Date: Wed, 14 Oct 1992 08:15:33 GMT

I want to buy thick ethernet cable and transceiver drop cable. 
I do not know how to test the quality of the cable. 
Can anyone suggest me the methods used to check the quality.
Thanking in advance.

						Vishwas Joglekar
						vishwas@cse.iitb.ernet.in
From: laut@alien.gici.com (Bill Laut)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Dividing up a subnet into groups
Date: 11 Oct 92 21:27:36 GMT
Organization: Gull Island Consultants, Inc.

In article <1992Oct7.171143.29286@ucsu.Colorado.EDU>, barr@tramp.Colorado.EDU (BARR DOUG) writes:
> Because of high traffic volumes we want to divide up a subnet into 
> different workgroups. We may do this with a bridge or a router.
> However, my first task is to take some statistics on who is communicating
> with whom. We have about 150 devices on this net. Does anyone know of a 
> good methodical way of dividing up this group. We obviously want to
> put workstations that have high amounts of traffic between them on the 
> same side of the bridge or router. I have a Sniffer and an old HP network
> analyzer.

I don't know what amount of growth you are expecting, but I'll elucidate 
what one client did.  When they were designing their new office, they wired 
every desk, nook, cranny, etc. with 10baseT.  For any given part of the 
office, the individual connections were brought out to a closet, where an 
ODS chassis is located.  Along with the individual fanouts were a some 
fiberoptic lines running back to the data center.

Generally, all of the 10baseT repeaters were configured to run through the 
ODS Ethernet backplane, connecting themselves together.  Then, the 
resignalling(?) module had a common fiberoptic connection linking it into 
the data center's routing ensemble.  

In cases of where "foreign" protocols (such as DECnet, LAT, Novell, etc) 
were required, those fanouts were plugged into a separate repeater module 
which was set the "standalone" position (so that it does not interact with 
anything else).  If needed, a separate fiberoptic connection was then run 
to the data center, into a data concentrator where other users of the same 
protocol would merge.

In short, without too much extra wiring, they were able to come up with a 
design that is extremely flexible and can easily be configured to meet 
almost any requirements.  What's nice is that if you have really serious 
network loading issues, something like this design can allow you to isolate 
present AND future hogs to their own subnets.


-- 
Bill Laut			Internet:  laut@alien.gici.com
Gull Island Consultants, Inc.	Phone:     (616) 780-3321
P.O. Box 627
Muskegon, MI  49440		>> "Usual disclaimers, apply within" <<
Newsgroups: comp.dcom.lans.ethernet
From: olson@anchor.esd.sgi.com (Dave Olson)
Subject: Re: Kalpana Etherswitch
Organization:  Silicon Graphics, Inc.  Mountain View, CA
Date: Sun, 11 Oct 92 21:46:22 GMT

In <1992Oct11.194519.11411@netcom.com> seifert@netcom.com (Rich Seifert) writes:
| In article <1992Oct7.170659.28586@ucsu.Colorado.EDU>, barr@tramp.Colorado.EDU (BARR DOUG) writes:
| > We have a subnet that is quite full (35% average usage during working hours
| > and 85% peaks). We are considering using a Kalpana ether switch to divide
| > up the traffic. I understand that the Kalpana has fixed some of the earlier
| > problems. Does anyone have any experience with this bridge (etherswitch)?
| 
| Remember that the switch will help you ONLY if the traffic patterns are
| "many-to-many", rather than "workstation-to-server". The switch will
| relieve this type of network congestion, but won't help you if a
| server is at all the bottleneck. 

In fact, if it is 'many clients to server' type traffic, devices like
the Kalpana can easily cause lots of problems, since it can't have
infinite buffering.  Think about what happens when each port with
clients sees the full bandwidth of an ethernet, and the server still
has the same old 10 Mbits/sec.  Unless the clients have small windows
(or there are very few of them per Kalpana port) you are in trouble
(packets get dropped; in fact, many of them can get dropped; this is
completely independant of how fast packets can be moved from one port
to another, although not independent of the amount of buffer memory).
You also lose collision detection across the Kalpana (or similar
device) ports, which tends to make the situation even worse.

Suffice it to say that on our nets, we have pulled Kalpanas out of most
of our nets where we have tried them (there is one net where it seems
to work fairly well, because of the traffic patterns).  This is my
personal perception of the situation, not an official statement of my
employer.
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
From: vhalkka@klaava.Helsinki.FI (Vesa Halkka)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Fanouts, multiport transceivers...
Date: 10 Oct 92 23:06:37 GMT
Organization: University of Helsinki

In <j=kp=a#@lynx.unm.edu> opus@pioneer.unm.edu (Colby Kraybill) writes:

>WTF is a fanout and how does it differ from a multiport transceiver?
>(except cost)

fanout is a term I have seen in digital electronics.. it says
how many gates you can drive simultaneously with one output.

a fanout box is connected to the segment with a normal
transceiver. And you can kind of increase the fanout of the one
transceiver from one to N, so that you can 'drive' N computers
with one transceiver.

The only functional difference to a multiport transceiver is that fanout
boxes don't need the ethernet at all.. they can be used
as a hub, at least if the 'real' transceiver port can
be fooled to think it is connected.. DEC DELNI has a switch 
for that.

--
Vesa Halkka                       -O___/ 
University of Helsinki CC:         (  /   	 vhalkka@helsinki.fi 
Centre for scientific computing:  ~~~~~  	 vhalkka@csc.fi
Newsgroups: comp.dcom.lans.ethernet
From: seifert@netcom.com (Rich Seifert)
Subject: Re: Found Network Diagnostic Book
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Fri, 16 Oct 1992 21:18:04 GMT

In article <75@fedfil.UUCP>, harris@fedfil.UUCP (harris) writes:
> 
> A few weeks ago I posted a request for a book to use to explain the output
> of protocol analyzers on an Ethernet.  A number of people sent me E-Mail
> requesting the same information.  I have just purchased a book on TCP/IP
> which was exactly what I wanted.  It is "Troubleshooting TCP/IP Analyzing
> the Protocols of the Internet" by Mark A. Miller, P. E.  I have not had
> a chance to read it yet but it includes a multitude of "Sniffer" trace
> files with complete explanations of their meaning.  It is published by
> M&T Books, 411 Borel Ave., San Mateo, CA 94402, phone 415-358-9500,
> list price $44.95.
> 
> I also have a lead on a similar book for Novell, but it is not yet in
> print.  If I get further details I will post them.
> 

The Novell book has been around for awhile:
  Analyzing Novell Networks, by Carl Malamud, and published by
VanNostrand, Reinhard also delves into the protocol details with
lots of Sniffer traces showing the internals of the packets.


-- 
Rich Seifert                    Networks and Communications Consulting
seifert@netcom.com              (408) 996-0922
                                (408) 996-2860 FAX
"... specialists in Local Area Networks and Data Communications systems"
From: bruce@camb.com (Barton F. Bruce)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Jumper settings of 3c501 network card?
Date: 12 Oct 92 02:36:22 EDT
Organization: Cambridge Computer Associates, Inc.

In article <1992Oct6.142314.49737@ccvax.ucd.ie>, bradshaw@ccvax.ucd.ie writes:
> Does anyone out there know the harware settings for the 3c501
> ethernet card? What do each of the jumpers represent?

I would see if they have a file that describes that card. Also their 
techtips directory has over 1400 files.

FTP to ftp.3com.com
From: freiss@neurotic.sni.de (Martin Freiss)
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Subnetting question...
Date: 16 Oct 92 10:33:40 GMT
Organization: Siemens Nixdorf Info.Sys. AG, Paderborn, Germany

In <1992Oct13.175219.3570@vpbuild> jessea@uucp (Jesse W. Asher) writes:

>In article <1992Oct9.180714.25050@sun1x.actc.res.utc.com> dowd@sun1x.actc.res.utc.com (Kevin Dowd) writes:
>>Does anyone have words of advice about breaking a class B network
>>into different sized subnets?  I know it's not provided for in 
>>rfc950, but I wonder if people do it anyway, and if so, what are 
>>the dangers?

>A word of advice - be very cautious about subnetting on non-byte
>boundaries.  This can be hazardous with things like DNS and can become a
>real maintenance nightmare.  I'd say that you should have a _very_ good
>reason before you subnet on non-byte boundaries.

There should be an explanation of your advice here. DNS has nothing
whatsoever to do with IP subnetting (IP being a network layer protocol,
and DNS being an application). We have successfully converted a Class B
net to subnets on a non-byte-boundary, and I fail to see where the problems
are? The standard allows it, I have never seen an IP implementation
break because of it, and everybody is happy.

One should do away with the myth that non-byte-boundary subnets are a
bad thing. This old saw belongs in the same drawer as the 'Ethernets
break on more than 30% utilization' folklore.

The original poster asked for advice on different size subnets in one
and the same IP network. The answer is it works (mostly), but has some
problems to do with the fact that routing from the 'bigger' subnets
to the 'smaller' ones is a problem, as hosts on the bigger subnets
cannot distinguish between the smaller networks.
If you have smart routers, you can probably make it work. Once OSPF
is available on end systems, it will work everywhere. For today, it works
but usually leads to sporadic strange routing errors if you're not
very careful.

-Martin

--
 Martin Freiss               | R&D computer center | freiss.pad@sni.de 
 Siemens Nixdorf Infosystems | Dept. STO SI 325    | NIC MF194
"Working in a team is difficult when you're omniscient."