HDTenEightyP/NetNews huggingface dataset:
From: "Brian Smith" <bsmith@nms001.ateng.az.honeywell.com>
Subject: Re: Bug reports, and this mailing list...
Return-Path: <bsmith@nms001.ateng.az.honeywell.com>
Date: 11 Jan 93 09:23:22 MST
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <9301111623.AA01835@nms001.ateng.az.honeywell.com>


> From cisco-forw@spot.colorado.edu Fri Jan  8 18:20:32 1993
> Date: Fri, 8 Jan 93 15:58:46 PST
> From: William "Chops" Westfield <billw@glare.cisco.com>
> To: cisco@spot.colorado.edu
> Subject: Bug reports, and this mailing list...
> Content-Length: 533
> 
> Just a reminder that the cisco@spot.colorado.edu mailing list (and the
> associated comp.dcom.sys.cisco Newsgroup) are user mailing lists that are
> NOT directly associated with cisco.  While the recent "what sort of troubles
> have you had with 9.1" dicussions are entirely appropriate, issues like
> "my router crashed and gave me this stack trace" would probably elicit
> better results if reported directly to cisco customer engineering, either
> by email (to customer-service@cisco.com), by phone, or by CIO.
> 
> Bill Westfield
> cisco Systems.
> 
Bill,

I'm sure this is true but the info is very helpful for us other users to know 
about.  Maybe people could send the problem to Cisco AND here?

			
			Brian Smith
			Honeywell CFSG
Newsgroups: comp.dcom.sys.cisco
From: C.Chaundy@its.unimelb.edu.au
Subject: Re:  Finding ROM version
X-Vms-Cc: IN%"cisco@spot.Colorado.EDU"
Content-Transfer-Encoding: 7BIT
Mime-Version: 1.0
Date: 13 Jan 1993 10:00:12 +1100
X-Vms-To: IN%"henryc@oar.net"
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <01GTGSGWB20Y8WVZ1M@ucsvc.ucs.unimelb.edu.au>

>Date: 12 Jan 1993 07:56:42 -0500
>From: henryc@oar.net
>Subject: RE:  Finding ROM version
>
>...
>
>The best thing I've found to do is to give the load useful names,
>so when I do a "show flash" you can readily tell what's there.  For
>example,
>
>...
>
>Hope this helps,

Not really!  I want to find out the version of the software in the *ROMs*
is (not the software currently running).  According to cisco, you cannot
find this out (although the bootstrap version apparently provides some
non-intuitive information).  I have asked that this be considered as an
enhancement request.

Regards, Chris Chaundy
Newsgroups: comp.dcom.sys.cisco
Subject: Re: DECnet areas
From: leonard@telcom.arizona.edu (Aaron Leonard)
Date: 6 Jan 93 18:06:12 MST
Reply-To: Leonard@Arizona.EDU
Distribution: world,local
Organization: University of Arizona Telecommunications

In article <1993Jan6.184259.8546@ferrari.nmc.ed.ray.com>, smiles@NMC.ED.RAY.COM (Kevin Ruddy)
writes:

| We have an AGS+ at each of three of our facilities.  Each AGS+ has about
| eight to ten Ethernet interfaces.  Each facility is a different DECnet area,
| and the AGS+ at the facility is the DECnet area router.
| 
| At one of our facilities, we are running out of DECnet addresses.  We have
| already allocated 750 of 1000 addresses, and at the rate we're using them
| we'll have used them all by this June.  We will be forced to move to a
| second DECnet area before the 1993 is out.
| 
| The only way I know to implement this second DECnet area is by using a
| separate piece of equipment -- basically, a second AGS+.  We'd really rather
| not do this.

Why not have a VMS system at that facility act as an area router to the
new area (or have several, for redundancy's sake?)  We've done this in
similar situations here, with no observable negative consequences.  Some
traffic may take a suboptimal path, but we haven't seen any unseemly
performance.

| Can the existing AGS+ do anything regarding this second area?  Can it act as
| area router for two different areas?  Are these in the plans for future
| Cisco releases?

I doubt it.  DEC keeps claiming that DECnet Phase IV will be "desupported
real soon" - at DECUS last, I think I heard something about summer '94 -
so why would a third party vendor want to devote resources to enhancing
their Phase IV features?

Aaron

Aaron Leonard (AL104), <Leonard@Arizona.EDU>
University of Arizona Network Operations, Tucson AZ 85721
Newsgroups: comp.dcom.sys.cisco
From: Omar Barazanji <barzanji@cisco.com>
Subject: Bug reports, and this mailing list...
Date: 8 Jan 93 17:30:41 -0800
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <9301090130.AA23783@last-call.cisco.com>




Just to add to this Bill, Customer Engineering technical assistance
center can be reached via email by using:

			tac@cisco.com

Omar Barzanji
cisco systems
customer engineering




   Date: Fri, 8 Jan 93 15:58:46 PST
   From: William "Chops" Westfield <billw@glare.cisco.com>

   Just a reminder that the cisco@spot.colorado.edu mailing list (and the
   associated comp.dcom.sys.cisco Newsgroup) are user mailing lists that are
   NOT directly associated with cisco.  While the recent "what sort of troubles
   have you had with 9.1" dicussions are entirely appropriate, issues like
   "my router crashed and gave me this stack trace" would probably elicit
   better results if reported directly to cisco customer engineering, either
   by email (to customer-service@cisco.com), by phone, or by CIO.

   Bill Westfield
   cisco Systems.

Newsgroups: comp.dcom.sys.cisco
From: Pasha Quadri <quadri@last-call.cisco.com>
Subject: Re: FDDI board refuses to work, 100% cpu load to boot
Date: 7 Jan 93 14:13:16 PST
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <CMM.0.90.2.726444796.quadri@last-call.cisco.com>



Hello Hans,

> I just installed our first FDDI board in our Cisco, and surprise..
> it doesn't work. It looks like it cannot enter into the ring. I had it
> installed at first in our ring with 3 Interphase FDDI boards, but when that
> didn't work I tried looping back the Cisco to itself. Even that did not
> work. I configured it:
> 	interface fddi0
> 	ip address 130.37.16.1 255.255.255.0
> 	no shutdown
> 

Loopback on FDDI is not supported in the version you are running. You
need at least 9.1 and the new ucode.



> The router is now very slow, the 'show proc' output shows that the PHY-A
> and PHY-B processes take all the time. I did a shutdown on the interface
> and the router is back to normal.
> 

It is making an attempt to complete the CMT state machine. Please
check the internal cabling between the applique and the FDDI card.
Did you run a debug of fddi-cmt-events ? Did you see an increment 
in the interface resets counter ?


#show hardware
> GS Software (GS3-F), Version 8.2(7) 
> Copyright (c) 1986-1991 by cisco Systems, Inc.
> Compiled Wed 13-Nov-91 17:45 by mlb
> 
lossus#show int fddi0
> 
> Fddi 0 is down, line protocol is down 
>   Hardware type is cBus Fddi, hardware address is 0000.0c02.1076
>   Internet address is 130.37.16.1, subnet mask is 255.255.255.0
>   MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
>   Encapsulation SNAP, loopback not set, keepalive not set
>   ARP type: SNAP, ARP Timeout 4:00:00
>   Phy-A state is connect, neighbor is unk, cmt signal bits 08/00, status HLS
>     Brk 5257, Con 5257, Tra 0, Nxt 5254, Sig 0, Join 0, Vfy 0, Act 0
>   Phy-B state is connect, neighbor is unk, cmt signal bits 20C/00, status HLS
>     Brk 5258, Con 5258, Tra 0, Nxt 5255, Sig 0, Join 0, Vfy 0, Act 0
>   CFM is isolated, token rotation 5000 usec, ring not operational
>   Upstream neighbor 0000.0000.0000, downstream neighbor 0000.0000.0000
>   Last input never, output never, output hang never
>   Output queue 0/40, 0 drops; input queue 0/75, 0 drops
>   Five minute input rate 0 bits/sec, 0 packets/sec
>   Five minute output rate 0 bits/sec, 0 packets/sec
>      0 packets input, 0 bytes, 0 no buffer
>      Received 0 broadcasts, 0 runts, 0 giants
>      0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
>      0 packets output, 0 bytes
>      0 output errors, 0 collisions, 4 interface resets, 0 restarts

I have opened case number 45267. Please refer to this when you
communicate to me on this problem.


Regards

Pasha Quadri
Cisco Cust. Engg
From: tli@cisco.com (Tony Li)
Newsgroups: comp.dcom.sys.cisco
Subject: Re: IGRP information on interfaces with secondary address
Date: 9 Jan 1993 02:17:35 GMT
Organization: cisco Systems, Menlo Park, California, USA
NNTP-Posting-Host: lager.cisco.com
Keywords: igrp, x25, secondary address, 9.0, 9.1

In article <C0Ip95.Cr8@orfeo.radig.de> Peter Radig
<peter@orfeo.rhein-main.de> writes: 
    The configuration is a AGS running 9.0(1) / 9.0(2.6) / 9.1(1.3) 
    
    	interface serial 3
    	encapsulation x25
    	ip address 192.125.1.9 255.255.255.252 secondary
    	ip address 192.125.253.2 255.255.255.0
    
    The reason I found was that all IGRP pakets send via broadcast on
    this interface had the secondary address as sender. 

I'm unable to reproduce this problem whatsoever.  Please send your full
configuration to tac@cisco.com.

Thanks,
Tony

-- 
abyss \*-'bis\ n 
  1 : the bottomless gulf, pit, or chaos of the old cosmogonies  2 a : an 
  immeasurably deep gulf or great space  b : intellectual or spiritual 
  profundity; also : vast moral depravity 3 a Border Intermediate System
Newsgroups: comp.dcom.sys.cisco
From: rfranken@cs.umr.edu (Richard Brett Frankenberger)
Subject: Re: IPX and NetBios routing/bridging?
Date: Sat, 9 Jan 1993 14:54:56 GMT
Organization: University of Missouri - Rolla, Rolla, MO

In article <1iklr2INNrct@apache.dtcc.edu> bob@hobbes.dtcc.edu (Bob Rahe) writes:
>  Anyway, for the IPX stuff everything seems fine, the catch is that on
>one of the file servers is a Racal-Interlan gateway.  This allows PCs to
>access TCP/IP thru a file server.  The catch is that altho it uses the
>Novell fileserver to store/load up the files to the pc for things like
>telnet, ftp etc., the actual traffic between the telnet process on the
>PC and the gateway software on the server is NetBios.  This is where I
>get lost, it appears that NetBios is only bridgeable.  Is that correct?
>If so, it would seem we either turn on bridging (yuck - how?) or we have
>to interconnect the lans with bridges or hubs or something, we will not
>be able to have different lans on different router interfaces.
>-- 
>-------------------------------------------------------------------------
>|Bob Rahe, Delaware Tech&Comm College | AIDS, Drugs, Abortion: -        |
>|Internet: bob@hobbes.dtcc.edu        |  - Don't liberals just kill you?|
>|CI$: 72406,525 Genie:BOB.RAHE        |Save whales; and kill babies?    |
>-------------------------------------------------------------------------

NetBIOS is generally not considered to be a network protocol.  It is more of an
API - a set of software interrupts used by programs to communicate across a LAN.
 
Several people make implementations of NetBIOS.  IBM is one company that does.
Their implementation uses the NetBEUI psuedo-protocol for communication across
the LAN between PC's.  You are correct that this protocol is NOT routable.  You
would need bridging.
 
Novell also makes an implementation of NetBIOS.  It uses IPX as the protocol
for communication across the LAN between workstations.  Since IPX is routable
(and you are already routing IPX), if you used Novell's NetBIOS, you would not
have to change anything on the routers.
 
Note that to a program running on the PC, both IBM's and Novell's implementation
are compatible.  They provide the same API to the programs.  On the network
side, however, they are different, and if one machine is running Novell's
NetBIOS and another is running IBM's, they will not be able to communicate.
 
Novell's implementation is not a separate product.  You should have gotten it
with all the other workstation programs.  It is NETBIOS.COM (or .EXE).
 
                   - Brett    (rfranken@cs.umr.edu)

Newsgroups: comp.dcom.sys.cisco
From: Phillip Remaker <remaker@cisco.com>
Subject: Re: MGS Power Supplies
Date: 8 Jan 93 12:51:40 PST
X-Mailer: ELM [version 2.3 PL11]
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <199301082055.AA00253@spot.Colorado.EDU>

> 
> Message:
> If the MAS-23 is an auto-ranging power supply from 110 to 240 volts, 
> then why is there a separate power supply listed for the UK (MAS-26)?
>

The UK has stricter electrical requiremnets (BABT) and the UK power
supplies are much more expensive because of that.

Thank the UK government.  Rather than saddle all of our users with that
expensive supply, we have a special UK model to placate the regulation
happy Brits. 8-)
  
> Also, is there a place or a way to identify each of the many MGS 
> power supplies floating around these days?  Most of them have only 
> manufacturer's model #s (not cisco's) affixed to them, so once the 
> shipping paperwork is discarded, you can't tell an MAS-23 from an 
> MAS-26 from an MAS-28 from a ...
>

Sure:

The MAS-21 is a Power-One. (150W)
    MAS-23 is a PSI power supply. (175W)
    (21A and 23A are the same supply, strapped for 220 V)

    MAS-28 is the CPI power supply.  This is the newest one for the M and C.
    It autoranges. (175W)

For the UK:

    MAS-25 is the AGS+, MAS-26 is the AGS/MGS, MAS-27 is the CGS.

    I think the UK power sipplies are all Farnell.


And, for completeness:

    The AGS 200W power supply is MAS-11.
    THE AGS+ 400W power supply is MAS-400. (Zenith, I think)  

> Tom
>  
> Tom Karolyshyn
> Data General Corp
> Westboro, MA 01580
> 508-870-7936
> 
> 
> 


-- 
Phillip A. Remaker remaker@cisco.com  
cisco Systems Customer Engineering  800-553-24HR
1525 O'Brien Drive  Menlo Park, CA 94025 
Newsgroups: comp.dcom.sys.cisco
From: Nicholas Thille <thille@cisco.com>
Subject: DECnet areas
Date: 7 Jan 93 07:48:14 -0800
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <9301071548.AA22076@lager.cisco.com>


>> We have an AGS+ at each of three of our facilities.  Each AGS+ has about
>> eight to ten Ethernet interfaces.  Each facility is a different DECnet area,
>> and the AGS+ at the facility is the DECnet area router.
>> 
>> At one of our facilities, we are running out of DECnet addresses.  We have
>> already allocated 750 of 1000 addresses, and at the rate we're using them
>> we'll have used them all by this June.  We will be forced to move to a
>> second DECnet area before the 1993 is out.
>> 
>> The only way I know to implement this second DECnet area is by using a
>> separate piece of equipment -- basically, a second AGS+.  We'd really rather
>> not do this.
>> 
>> Can the existing AGS+ do anything regarding this second area?  Can it act as
>> area router for two different areas?  Are these in the plans for future
>> Cisco releases?
>> -- 
>> Kevin.Ruddy@NMC.ED.RAY.COM
>> 

Cisco routers have offered level 1 and level 2 (area) DECnet routers for
some time.  I don't know when the support was initial done, but it has been
there since release 8.2.

The below configuration commands are described in chapter 12 in the Release
9.0 and Release 9.1 router manuals.  I suspect the commands are the same in
earlier releases, but check the DECnet chapter just to be sure.

To configure the cisco router as a level 1 router use the command:

	decnet node routing-iv

To configure the cisco router as a level 2 (area) router, use the command:

	decnet node area

Regards,

Nick Thille
Engineering 
cisco Systems, Inc
Organisation: European Space Operation Centre (E.S.O.C)
Date: Tuesday, 12 Jan 1993 10:31:38 CET
From: <RHUNTER@ESOC.BITNET>
Newsgroups: comp.dcom.sys.cisco
Subject: Re: DECnet areas
Distribution: world,local
 <1993Jan6.180614.4212@arizona.edu> <93008.084759RHUNTER@ESOC.BITNET>

I have done some more digging into the validity of 2 areas on 1 Ethernet.

Page 2-27 of VMS Networking Manual april 88 for VMS v5.0

"2.4.4.3 Area Routing on Ethernet
All nodes on an Ethernet need not be in the same area; you can configure
more than one area on a single ethernet. The areas on the same Ethernet are
logically seperate from each other.....
Section A.6 illustrates area routing on an Ethernet"

looks like everything will be OK.

Just a reminder of the problem:
Is it possible to run more than 1 DECnet area in a Cisco?

I think you use the Address Translation Gateway to start two processes
> decnet 0 routing
> decnet 0 node-type area
...
but you do NOT configure any translations....
the 2 routing processes should then run seperately, and only communicate
via the common Ethernet interfaces.

It then becomes a question of how many Ethernets you need to share areas
on, as you need to use 2 interfaces per Ethernet.

Once again, a reminder that this comes untested!

Ray Hunter
RHUNTER@ESOC.BITNET
Cray Systems on Contract to the European Space Agency
#include <std.disclaimer>
Newsgroups: comp.dcom.sys.cisco
From: Pasha Quadri <quadri@last-call.cisco.com>
Subject: Re: Routers and NFS traffic
Date: 5 Jan 93 10:03:24 PST
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <CMM.0.90.2.726257004.quadri@last-call.cisco.com>


Hello Mike,

> Some colleagues and I were discussing a subnet design the other day, and
> someone said that, for performance reasons, one shouldn't put a router
> between two hosts that have a "lot" of NFS traffic between them.
> 
> The reason given was that the router would have to decode every UDP packet
> in order to route it correctly, thus introducing unacceptable delays during
> heavy file transfer periods.
> 
> It is my impression that a decently powered router (like maybe an MGS) would
> be able to handle bursty, UDP-intensive applications like NFS with no problem.
> 

It is OK to NFS across networks that are ether-to-ether via a cisco
but do avoid it if you want to do it across a WAn that does not
consist of a full T1. If you see a lot of retarnsmissions, you should
use rsize and wsize parameters of mount to select smaller
transmissions. The 8K UDP packets sent by NFS are always fragmented to
begin with. Since most routers today match the ethernet mtu on serial
lines  and therefore additional fragmentation is unlikely to occur.
A protocol like RFS (I think it is developed by AT&T), based on TCP
and actually runs over streams which means, you can run it over UDP,
TCP, CLNS etc is maybe what is needed for such applications !? 




> Can anyone give me some insight on this?
> 
> Please email responses, and thanks in advance.
> 

> Mike Cantu
> mike@nit.PacTel.COM


Regards


Pasha Quadri
Customer Engg.

Newsgroups: comp.dcom.sys.cisco
From: smiles@NMC.ED.RAY.COM (Kevin Ruddy)
Subject: DECnet areas
Organization: Equipment Division, Raytheon Company
Date: Wed, 6 Jan 93 18:42:59 GMT

We have an AGS+ at each of three of our facilities.  Each AGS+ has about
eight to ten Ethernet interfaces.  Each facility is a different DECnet area,
and the AGS+ at the facility is the DECnet area router.

At one of our facilities, we are running out of DECnet addresses.  We have
already allocated 750 of 1000 addresses, and at the rate we're using them
we'll have used them all by this June.  We will be forced to move to a
second DECnet area before the 1993 is out.

The only way I know to implement this second DECnet area is by using a
separate piece of equipment -- basically, a second AGS+.  We'd really rather
not do this.

Can the existing AGS+ do anything regarding this second area?  Can it act as
area router for two different areas?  Are these in the plans for future
Cisco releases?
-- 
Kevin.Ruddy@NMC.ED.RAY.COM
Newsgroups: comp.dcom.sys.cisco
From: Bruce Pinsky <bpinsky@cisco.com>
Subject: Re: RFC 951 and BOOTP
Date: 5 Jan 93 16:39:22 -0800
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <9301060039.AA21050@last-call.cisco.com>

W. Smith writes:

==>
==>FC 951 states that routers can be configured to forward BOOTP
==>requests. How does cisco handle such requests? Are the packets
==>forwarded as-is or are they altered in some way? Does the 
==>router need any specific parameters set or is it a default
==>process in the router software itself? I'm trying to determine
==>how interoperable cisco is with other router vendors.
==>

cisco routers do not forward bootp broadcasts by default.  To forward bootp
(and several other UDP broadcast-based protocols), the router has a command
call ip forward-protocol udp.  This allows bootp to traverse the router.

Hope this helps...

+-------------------------+-----------------------+---------------------------+
+      ||        ||       +                       + Bruce Pinsky              +
+      ||        ||       + Cisco Systems, Inc.   + Customer Engineer         +
+     ||||      ||||      + 1525 O'Brien Drive    + Phone: (800) 553-24HR     +
+ ..:||||||:..:||||||:..  + Menlo Park, CA        + Fax:   (415) 903-8787     +
+   Cisco Systems Inc.    +                       + E-mail: bpinsky@cisco.com +
+-------------------------+-----------------------+---------------------------+
|                 ** The Science of Networking Networks **                    |
+-----------------------------------------------------------------------------+
Organization: St. John's University
Date: Mon, 11 Jan 1993 15:45:53 EST
From: Michael S. Holtzman <HOLTZMAN@SJUVM.BITNET>
Newsgroups: comp.dcom.sys.cisco
Subject: Kermit file transfer thru cs-516

Greetings.  We are using a cs-516 as a terminal server.  However there seems
to be a file transfer buffer size limit imposed by the Cisco.   The maximum
packet size for downloads is about 530 (bytes) and for upload about 120.

How can I configure the cs-516 to allow bigger packet sizes??  I would like
to get the limit in both directions up to around 2000.  Thanx in advance.
Newsgroups: comp.dcom.sys.cisco
From: Robert Snyder <snyder@cisco.com>
Subject: Re: IP Accounting Limits 
             <C0HovB.7nF@news.ucs.mun.ca> 
Date: 07 Jan 93 11:01:40 PST
X-Note1: message-id generated by recnews
X-Note2: mail msgid was   <9301071901.AA12632@wolf.cisco.com>

All the ip accounting counters are unsigned 32 bit numbers.
Does this help?
Robert
cisco eng

> Can anyone tell me the maximum value that can be stored in
> the "Bytes" field of the IP Accounting database?
From: wittmann@engr.wisc.edu (art wittmann)
Newsgroups: comp.dcom.sys.cisco
Subject: Pre-FDDITalk compatibility....
Date: 6 Jan 93 19:55:36 GMT
Organization: College of Engineering, Univ. of Wisconsin-Madison
Originator: wittmann@muskie.engr.wisc.edu


We're trying to get some netware servers on an FDDI ring.  Everything
works except appletalk.  The router's FDDI interface reports that it
is in pre-FDDITalk compatibility mode.  I suspect that this is the problem.
The question is; how do I get the router into FDDITalk compatibility mode?

Thanks,
Art

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Art Wittmann                                  Phone: (608) 263-1748
Associate Director                            Email: wittmann@engr.wisc.edu
Computer Aided Engineering Center                or: wittmann@cae.wisc.edu
University of Wisconsin, Madison
Newsgroups: comp.dcom.sys.cisco