HDTenEightyP/NetNews huggingface dataset:
From: szc@.IMSI.COM (Simon Chan)
Newsgroups: comp.dcom.sys.cisco
Subject: Need help with TACACS
Date: 3 Sep 92 15:06:55 GMT
Distribution: usa
Organization: Investment Management Services Inc., NYC
Originator: szc@titan

I am looking for help on installing/configuring the tacacsd for
user/password verification on a Cisco STS-10 Terminal Server.

I've downloaded the code from UUNET, but when I run xtacacsd, it
decided to crash and close my xterm with it.

Can someone help  ??


Thanks in advance.

-Simon
-- 
        Simon Z. Chan - Sys. Engineer	|   szc@IMSI.COM
 Investment Management Services, INC.   |   (212) 339-2786 phone
        12 E. 49th Street, 35th Floor	|   (212) 339-2854 fax
                   New York, NY 10017	|   Dont't Panic!
Newsgroups: comp.dcom.sys.cisco
From: Vince Fuller <vaf@Valinor.Stanford.EDU>
Subject: Re: ip ospf cost var
Usmail: Pine Hall 115, Stanford, CA, 94305-4122
Date: 15 Sep 92 15:55:36 PDT
Office: Spruce Hall F15, (415) 723-6860

    >What value can I use for the cost variable for DS3 serial links?
    
    >-- 
    >Regards,
    >Bill Manning         bmanning@rice.edu        PO Box 1892
    > 713-285-5415         713-527-6099	       Houston, Texas
    >   R.U. (o-kome)       			        77251-1892
    
    
    You can use the formula  cost = 10^8/bandwidth

Actually, you can use anything you want for the cost, but the default value
will be 10^8/45x10^6 = 2.

	--Vince
Newsgroups: comp.dcom.sys.cisco
From: a-steiner@nwu.edu (Albert Steiner)
Subject: Re: Using a high-speed modem on an ASM terminal server.
Followup-To: comp.dcom.sys.cisco
Organization: Northwestern University
Date: Tue, 8 Sep 1992 13:55:44 GMT

In article <1992Sep2.203948.25107@nmt.edu>, ray@nmt.edu (Ray Piworunas)
wrote:

> I can't establish a connection to the ASM at 19200-baud, nor at
> 38400-baud.  From looking at the ASM port (using sh li 40) at various
> times during the connection attempt it appears the ASM is in its
> autobauding mode.  It can't seem to lock on to the right speed.
> Occasionally it will show that the line has received a BREAK.
> 
> I have tried setting the ASM line to a speed of 38400 instead of
> autobauding but that didn't help any with the attempt to connect at
> 38400.  (I didn't try a slower speed connection with the ASM port at
> 38400 since the 38400 connection didn't work).
> 
I have used the following settings for high speed modems.
first a general setting, then a specific setting for particular modems.
Be sure you set your modems to keep the same DTE speed, 38400 or whatever,
there is usually a setting for the modem, the speed is set then by the AT
command.
You will want to save the speed, so that on a power out, the modem comes
back at the same speed.

line 1 64
    access-class 10 in
    access-class 10 out
    flowcontrol hardware
    stopbits 1
    modem ri-is-cd
    terminal-type vt100
    exec
    exec-timeout 1
    disconnect-character 0
    session-timeout 30 output
    escape-character 29
    dispatch-character 13
    dispatch-timeout 30
    location vogelback
    no password
    autobaud
line 5 8
    location 71500 8N Passworded Slip
    login tacacs
    no autobaud
    speed 38400
    databits 8
    parity none
    no escape-character

Manager, Networking
Albert Steiner      a-steiner@nwu.edu     708-491-4056
Academic Computing and Networking Service
Northwestern University  2129 Sheridan Road
Evanston, IL  60208      USA
From: cawilco@afterlife.ncsc.mil (Chris A. Wilcox)
Newsgroups: comp.dcom.sys.cisco
Subject: Problem with syslog-style logging (AGS+)
Summary: Anybody doing this currently?
Date: 8 Sep 92 13:10:03 GMT
Organization: The Great Beyond


I am having a problem with getting syslog-style logging to
work. I have an AGS+ (PROM software version 8.1(19), and
yes, I know I'm way behind :-) that I have enabled logging
on, and I'm sending it to our loghost. However, no messages
are appearing in the logs. I have checked /etc/syslog.conf
on the loghost, rebooted the system, and double-checked the
configuration on the AGS+. Everything looks kosher, yet
nothing is being logged. Any ideas?

A related question: just what constitutes an informational
message or above? We have had logging enabled on the AGS+
for over a week, and it thinks it's seen exactly nine
messages. I would have expected a few more than that...

Thanks in advance for any help.
-- 
***************************************************************************
Chris Wilcox       Email:cawilco@afterlife.ncsc.mil        Dept. of Defense
  None of the above statements necessarily represent the views of the DOD.
"I was raised to be charming, not sincere." Prince Charming, Into the Woods
From: jzwiebel@pgl-devsvr.den.mmc.com (John Zwiebel (303)977-1480)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: IP helper address/bridging/FDDI
Date: 14 Sep 92 21:56:10 GMT
Organization: PAGE @ Martin-Marietta

It turns out to be a combination of things that make this work the way it
does.  I have 6 AGS+ systems on the FDDI ring.  One has a cbus 2 and an FCIT
One has a cbus 2 with FCI and the rest are cbus 1 with FCI.  All are
connected to an FDDI ring.  All are bridging.  The FCIT card is doing
ethernet to FDDI translation bridging and ignoring the bridge packets from
the rest of the router (through the FDDI interface only)  This is working
well.

I believe that clients on the FCIT router have to have the UDP spanning tree
enabled to pass the packet to the FCI/cbus2 router which then generates
a ip helper packet.  It is a rather unique condition.  If anyone has any
interest in knowing more send me email
Newsgroups: comp.dcom.sys.cisco
From: bmanning@is.rice.edu (William Manning)
Subject: Re: ip ospf cost var
Date: 15 Sep 92 12:50:50 CDT
X-Mailer: ELM [version 2.3 PL11]


Thank you.  Now, what is the recommended cisco default value
for the ip ospf cost xxx, where xxx is a DS3 (45mbps) link?


-- 
Regards,
Bill Manning         bmanning@rice.edu        PO Box 1892
 713-285-5415         713-527-6099	       Houston, Texas
   R.U. (o-kome)       			        77251-1892
Newsgroups: comp.dcom.sys.cisco
From: jzwiebel@pgl-devsvr.den.mmc.com (John Zwiebel (303)977-1480)
Subject: IP helper address/bridging/FDDI
Organization: PAGE @ Martin-Marietta
Date: Fri, 11 Sep 1992 15:32:53 GMT

I'm working on getting FDDI translation bridging installed on my network.
(I want to thank Eric Decker & Lee Pang of cisco for their help in this.)
Last night I discovered a problem with ip helper-addresses and NIS that I
think I should pass on and ask if anyone else has seen the problem.

I switched my routers from running 8.3(3) to 9.1(0.14).  I discovered, after
two days, that NIS clients that lost the bind to their server (generally because
they were being rebooted) could not recontact any server.  I could still ypset
to a server.  I looked at my FDDI ring lanalyzer and discovered that the one
NIS broadcast from the client looking for the server was being bridged onto
the FDDI ring (you have to have an FCIT card and cBus2 for this to happen).  
This one broadcast would generate a 'ministorm' because every host on the ring
would forward a copy of that packet.  Since the IP address was set to broadcast
only on the physical network (xxx.xxx.xxx.255), the hosts routed the packet 
back to where it came from.  There were no ip helper packets forwarded by the 
cisco.

By turning on "ip forward-protocol spanning-tree", I was able to get the router
to generate packets directed at the "ip helper-address" or the NIS servers.  
This would _not_ prevent the bridged storm described above, but the clients
can now bind.

I tried changing the broadcast address of one of the clients to xxx.xxx.255.255.
This _seems_ to have stopped the storm.  I can still get clients to BIND.  This
is going to require some further testing on my part to be sure of what it 
happening.

An important bit of information, All of the Router Ethernet Interfaces are
configured "encap SNAP", "arp SNAP", "no arp ARPA".  All of the clients are
configured to use 802.3 vs DIX (Ethernet2).  

Has anyone else seen this problem?  If so please try to provide me with the
circumstances via email.

John Zwiebel
Newsgroups: comp.dcom.sys.cisco
From: J.Hayward@utexas.edu (Jeff Hayward)
Subject: Link level vs routing timeouts
Date: 10 Sep 92 11:44:11 CDT
X-Mailer: ELM [version 2.3 PL11]

What do folks do when they want a router to router path to use a LAN
path as primary, with fallback to a point-point circuit?  Here's
the diagram:

         Campus                             Campus
     ================                    =============
           |                                  |    |
          +--+                               +--+ +--+
          |R1|------------T1-----------------|R2| |R3|
          +--+                               +--+ +--+
           |                                       |
        802.3/4 bridge                           802.3/4 bridge
        ==================802.4 MAN===========================

If the MAN loses connectivity between R1 and R3 the routers at each
site will detect nothing until the routing layer times out (many
minutes).  However, if the T1 were to fail they would detect it within
seconds via the link-level hellos and initiate a routing change
accordingly.  The cisco link-level check of a LAN only verifies that
the box can talk to itself, not its peers on the LAN.  What can I do
to get decent fail-over times for this MAN/T1 situation?

Thanks,
Jeff Hayward
Office of Telecommunication Services
The University of Texas System
Newsgroups: comp.dcom.sys.cisco
From: ddb@TorreyPinesCA.ncr.com (Drew Bullard 3566)
Subject: Bridging question
Organization: NCR (Torrey Pines Development Center)
Disclaimer: This posting does not neccessarily reflect the opinions of NCR.
Date: Wed, 9 Sep 92 18:26:14 GMT


 Howdy,

  Question? 

  Our internal network, not including  WAN, has 4 routers all in bridging mode (no spanning tree), don't ask why we don't subnet and route. All the traffic is IP. The routers are connected via an ethernet cable backbone. 
  
  Here's the question. I have an AGS+ with 3 6 port MEC boards. If I were to connect the other 3 routers to the cisco and use it as the backbone, would I see better performance, assuming that now it would be a high speed bus backbone? Would it be better to place the other 3 routers on 1 card and rely on the packet switched rate between ports or spread them across cards and rely on the bus?

  As a side question while I have your ear, what are the performance characteristics on the Cisco with respect to bridging vs. routed IP traffic throughput?

  FYI, we tried this scenerio using a Wellfleet at the top of the tree and performance sucked between leaf routers.

  The objective here is to improve the backbone performance with the existing hardware. FYI, the routers are, 1 Cisco AGS+, 2 Wellfleets, 1 Alantec.

  FYI,

  GS Software (GS3-BF), Version 8.3(1), 
  Compiled Mon 21-Oct-91 22:15 by block

  System Bootstrap, Version 4.4(1), 

  hub4 uptime is 1 week, 5 days, 1 hour, 11 minutes
  System restarted by power-on
  Running default software

  CSC3 (68020) processor with 4096K bytes of memory.
  Bridging software.
  1 cBus controller.
  18 Ethernet/IEEE 802.3 interface.
  Environmental Controller.
  64K bytes of multibus memory.
  64K bytes of non-volatile configuration memory.
  Configuration register is 0x181


  thanks for the advise,

  Drew Bullard
  ATT NCR Large Computer Products Division
  Torrey Pines Development Center
  Drew.Bullard@torreypinesca.ncr.com
  (619) 597-3566
From: talbot@captain (John Talbot)
Newsgroups: comp.dcom.sys.cisco
Subject: Frame Relay
Date: 9 Sep 92 17:21:48 GMT


Subject: Frame Relay
Newsgroups: comp.dcom.sys.cisco



OPEN QUESTION  TO IMPLEMENTERS OF LARGE 
FRAME RELAY NETWORKS


Has anyone noticed the lack of control you
have in selectively advertising and learning
routes on frame relay interfaces ?  Although
the usual distribute-lists apply, frame relay
is unique in that you have >1 router at the
other end of the link.  Now assume you have
100-200 routers out there, somewhere, at non-company
owned sites.  Although you own the boxes, you can't
guarrantee their security at these remote sites.
Wouldn't it be beneficial to be able
to have total control of the routing updates at
the hub router(s) at your site ?  This is not possible
with Cisco's current implementation (not possible with
other implementations either).

Frame-relay is very "loosey goosey" in how the router
verifies and controls routing updates.  A single misconfigured
router at a client site could disable your entire network, and
make it very difficult to locate the problem.  These are the
issues we're currently dealing with.

I'd like to see Cisco enhance the control mechanisms
to be suitable for a *large* frame-relay environment.  

Here's a suggestion.  Create a frame-relay version of
the distribute list feature, this time using extended
IP access lists. I should preface this discussion with
the comment that Cisco sees no value in providing routing
control beyond what is already provided.

Assume topology as below, netmask 255.255.255.0
My router (my site) is address 129.10.10.10.
Each client side router has >=1 subnet to tell me about.
These routers can not be assumed to be secure.

	R 129.10.10.1    R 129.10.10.2  R 129.10.10.3
	|		 |		|
	|		 |		|
	|		 |		|
	---------------------------------------
     ----				    ------
		cloud
     ----				    ------
	---------------------------------------
			|
			|
			|
			R 129.10.10.10
			  (my router, my datacenter)


access-list 101 permit 129.10.10.1 0.0.0.0  129.10.20.0 0.0.0.0
access-list 101 permit 129.10.10.2 0.0.0.0  129.10.21.0 0.0.0.0
access-list 101 permit 129.10.10.3 0.0.0.0  129.10.22.0 0.0.0.0
access-list 101 permit 129.10.10.3 0.0.0.0  129.10.23.0 0.0.0.0

router igrp xxx
frame-relay distribute-list 101 in [ serial 0 ]

This would restrict which subnets you will learn from which
routers.  This could similarly be achieved with the "distance"
feature, as mentioned by Bob Albrightson of Cisco.  However, this
distance feature relies on a single access list for each router
which limits the number of routers to 99 because of the limit of
the number of standard IP access-lists.   An AGS+ with 4,5
frame-relay links shouldn't be limited to 99 endpoints.  Throwing
more routers and links at the problem is not the answer either.

I believe this feature, although not well received by Cisco, would
work well, be easily understood, and be consistent with their
former approaches to routing control.  

I'm interested in hearing comments.

Thanks.
From: hedrick@athos.rutgers.edu (Charles Hedrick)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: CAP 6.0 PL126 on RS/6000 and CISCO 9.0(1.11)
Date: 10 Sep 92 05:42:47 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

a0061@rrz.uni-koeln.de (Claus Kalle) writes:

>I am trying to get CAP 6.0 PL126 running on AIX 3.2 with a CISCO IPTALK
>configuration doing the encaps/decapsulation. The CISCO keeps telling me
>about invalid Ethertalk packets encapsulated in IPTALK when I run atistest
>under AIX 3.2. And atistest complains that atis is not running ?.
>If I leave out the bridgenode in atalk.local, at least atistest can register
>its name, but since no bridge, no connectivity to the outside.
>Did anyone get such a configuration up and running ?

We have moved most of our IPtalk hosts to Ethertalk, but we have a
couple of IPtalk left.  I can't tell for sure, because the one I know
about is down at the moment, but last time I checked, it was working
with 9.0(1.xx), for some xx fairly near 11.
Newsgroups: comp.dcom.sys.cisco
From: simpsong@dns0.bham.ac.uk (Glyn Simpson)
Subject: Re: Advertising Static routes
Date: Wed, 09 Sep 1992 08:04:22 GMT
Reply-To: G.Simpson@bham.ac.uk
Organization: The University of Birmingham, England
X-Newsreader: Tin 1.1 PL5

Paul Traina (pst@cisco.com) wrote:
> In article <1992Sep07.155935.14888@rs6000.bham.ac.uk> G.Simpson@bham.ac.uk writes:
> >Can anyone tell me out there whether it is possible to advertise static
> >routes which have:
> >	1. Been defined as secondary addresses on an interface
> >	2. Been defined using the 'IP ROUTE' command and a weight.
> 
> try 'redistribute static'
> 
> as in
> 
> router rip
> network x.x.x.x
> redistribute static

That doesnt really seem to work - i already have that there. So far, i
have:

router rip
network 147.188.0.0
redistribute static
default-metric 1


then a couple of passive interfaces. I think the problem could be that 
it doesnt transmit subnets of the 147.188 network ?? (Could be wrong here).

--
Glyn Simpson, Systems Officer,  //  Voice: +44 (0) 21 414 6575
University of Birmingham        //  Fax:   +44 (0) 21 414 3952
Email: G.Simpson@bham.ac.uk     //  NIC Handle: GS56
Newsgroups: comp.dcom.lans,comp.dcom.lans.ethernet,comp.unix.questions
From: jmoore@ssd.kodak.com (James H. Moore 726-0322)
Subject: source of ka9q
Originator: jmoore@cabbage
Organization: Eastman Kodak
Date: Thu, 10 Sep 92 17:49:43 GMT

Again a naive posting.  I am still grappling with using telnet to
get from a PC to a Unix workstation.  Some of you responded with
suggestions of NCSA telnet and the Clarkson packet drivers.  Getting
telnet from NCSA is terrific.  Finding the packet drivers has been a bit 
more challenging.  I went to OMNIGATE at Clarkson, and found a directory
that had a had a This.Stuff.Is.Outdated file in it.  I saw that other 
major sites were still getting them in a variety of file structure
formats.  I ended up back are at Clarkson on sun.soe.clarkson.edu.
there it was packet-drivers  (not like the pktdrvr directory off of 
oak.oakland.edu).  But on closer inspection, I found that packet-drivers
is a link to ka9q.  We are a commercial organization, and I like to know
what is mirrored from where.  I figured that the Clarkson package
drivers originated at Clarkson, but where does ka9q originate, or
who is the author.

All of your help is appreciated!

Thanks!

					Jim

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - James H. Moore, The Software Warehouse, Eastman Kodak Co. 726-0322  -
- -  jmoore@pixel.kodak.com, PROFS: EKSMTP(JMOORE)  VMS: UX047A::JMOORE -
- -  May God bless you, in Jesus' name for blessing me with your help - -
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: Help! QEMM & Ethernet conflict
From: Aengus Lawlor <RBYAML@rohvm1.rohmhaas.com>
Date: Thu, 10 Sep 1992 09:19:36 EDT
Distribution: usa
Organization: Rohm and Haas Company

In article <1992Sep10.024124.15295@news.columbia.edu>,
kra@cunixa.cc.columbia.edu (Kenneth R Aron) says:
> I am a relative novice at nets, currently involved in a
>pilot program for an Ethernet network here at Columbia
>University.  I am running and ALR 25386DX w/DOS 5.0 & QEMM.  If
>QEMM is resident, the Ethernet software will lock up.  Only if I
>bypass QEMM can I use the net.  The installer told me to have QEMM
>exclude D00-E00, but that didn't do the trick.  If anyone has a clue
>how to fix this, drop me a line.  If you need more info (ie,
>program names, etc) e-mail me as well.  Thanks.
Some (most?) ethernet cards have a ROM or RAM in the area that
QEMM uses to load stuff high.  Because this is often only initialized,
or turned on when the network s/w is run, QEMM doesn't see it at
start up, and it may have used it for something else.  You need to
use an eXclude parameter for QEMM to tell it to leave that section of upper
memory alone.

How do you know what addresses are involved?  Run the diagnostic program for
the card, if available.  (And read the DOCs to see what the options are).
Quick and dirty, run QEMM ANALYSIS MAP just after the network s/w, to see if
it recognises that some memory needs to be excluded.  You could even ask the
people who installed the card how it is configured.

One thing that might work though, is to change your current eXclude
statement to D000-E000, as D00 is in the 1st 64K or RAM, not in the Upper
memory area.

>Ken > > > >Kenneth R.  Aron NYS EMT-Defibrillation | | / /
>kra@cunixa.cc.columbia.edu Columbia Area Volunteer Ambulance | |/ / >
>Columbia University, NYC | |\ \
>"EMTs do it with patience" | | \ \
Aengus
--
RBYAML@ROHMHAAS.COM                    Aengus Lawlor
RBYAML@ROHVM1.BITNET                   (who used to be ALAWLOR@DIT.IE)
"How about some of that famous Dublin wit, Barman?"
"Certainly, sir. Would that be Dry or Sparkling?"
From: harvey@indyvax.iupui.edu
Newsgroups: comp.dcom.lans.ethernet
Subject: Re: 802.3 Non-Compliance (summary and lesson)
Date: 9 Sep 92 20:36:19 GMT
Organization: Purdue University, Indianapolis

In article <1992Sep8.222237.7387@samba.oit.unc.edu>, shava@hermes.oit.unc.edu (Shava Nerad Averett) writes:
> In article <JKT.92Sep3134856@seneca.SED.Provo.Novell.COM> jkt@SED.Provo.Novell.COM (Jack Thomasson) writes:
>>odi-based drivers (v3.11+ and workstation) can be configured for
>>ethernet_802.3 (draft standard mentioned above, also know as "raw"),
>>ethernet_ii, ethernet_802.2 (fully compliant and a good choice, hint,
>>hint), and ethernet_snap (ethernet_802.2 + snap extension).
>
> ethernet_802.2 is fine *IFF* you use only IPX via ODI on your workstation,
> or if you are using IPX and IP using LAN WorkPlace.

No, you are *not* limited to one encapsulation per physical adapter as this
statement seems to imply.

>                                                      If for any reason
> you want to use packet drivers on top of ODI (for instance, to save
> memory...), the ODIPKT packet driver interface will not support 802.2.

But ODIPKT *will* support Ethernet II, and you *can* specify different
encapsulations for IPX and IP.  For example, suppose you want to use 802.2
for IPX and Ethernet II for IP (the latter via ODIPKT).  NET.CFG would look
something like this for a (mumble here) adapter:

Link Driver mumble
	Frame Ethernet_802.2
	Frame Ethernet_II
	Protocol IPX E0 Ethernet_802.2

When the mumble MLID is loaded, it will create two "logical interfaces" - one
for each encapsulation, numbered in the order listed.  The TSR load order will
be something like:

LSL
mumble
IPXODI
NETX
ODIPKT 1 96

The "1" argument to ODIPKT tells it to register with the second logical
interface (0=1st, 1=2nd, etc.).  This will be the one using Ethernet II
because that's what we specified in NET.CFG.

> At least, this is our experience.  We are still going to ethernet_ii,
> campuswide.  We doubt TCP/IP, which runs ethernet_ii, is going to disappear
> very soon, so it seems like a fairly safe bet.

Yes, all the IP networks I've seen still use Ethernet II.  If one must use
an IEEE 802 encapsulation for IP, use 802.2 SNAP (see RFC 1042).

> Note that even the NetWare documentation for 3.x, in the sysadmin guide,
> under LOAD, mentions that you should only use the 802.3 default frame
> type on a network that is only carrying NetWare.  But no mention of this
> caveat is made in the installation guide...

Heh.  Someone at Novell once told me that the only reason they didn't have
guilt feelings about "raw 802.3" is because they didn't work there when it
was invented... :-)

> --
> Shava Nerad Averett				shava_averett@unc.edu
> /*  all materials (c)1992, Shava Nerad Averett, and have nothing significant
>     to do with the University of North Carolina, a mostly owned subsidiary
>     of the NC Legislature, a mostly owned subsidiary of the DOT.      */
--
James Harvey    IUPUI OIT Technical Support
harvey@iupui.edu  uucp: iugate!harvey  bitnet: harvey@indyvax