[comp.dcom.sys.cisco] Looking for Clues

GREENEBL@PEOCU1.NAVY.MIL (BARRY) (12/21/90)

Hello CISCO Gurus,

I'm looking for some clues to a CISCO configuration (or 
hardware)problem I'm having with the Internet (MILnet side).  My 
system manager took off on vacation and left this for me to take care 
of.  We've got a system that just came on line a few months ago, and 
the Internet connection has never worked right.

THE PROBLEM: Our PSN is getting a lot of CRC and frame errors.  Our 
TAC users have a window of about three minutes of good transmission 
with out host before the transmission from our host stops dead for 
about 15 to twenty minutes.

Our system manager (the one that's now on vacation) has talked to 
CISCO and DCA for about a month.  Yet, the problem still persist.

I've been working with DCA the last couple of days.  We t-shoot the 
line, the modems, and the cable going from our modem to our CISCO.  
All are excellent.  I removed the ethernet side of the CISCO (just 
unplugged) and check with DCA.  Same problem.  When you log into the 
CISCO from a TAC, you get exactly the same problems as you do when you 
log into our host. 

CISCO send a new serial card yesterday, I swapped it out with old one.  
DCA is getting the same errors.


SYSTEM CONFIGURATION: We have a CISCO model MGS2 with a serial card 
(for the Internet) and one ethernet connection (going to our two VAX 
6210s).  Our link with the Internet (MILnet to be exact) is a 19.2 
line.  We are using VMS 5.3, Process Software's TCPware for VMS, and 
Novell's Netware for VMS (bridging into the ethernet to link our LAN 
and VAXs).

Our system manager has consulted with CISCO and tried some tuning, but 
no luck.

The main question I have are:

1. What parameters can I mess with the isolate the problem?

2. How can I see the problem?  Everything I've tried shows no errors, 
yet DCA is getting errors (CRC and frame).

3. Are there any CISCO gurus out there I can correspond directly?

4. We replaced one card already (the serial card).  Could this be a 
hardware problem?

5. Could it be a problem with TCP, ethernet, etc. consuming CISCO 
processing time?


I'm interested in any and all advice.  Please send replies to me (no 
since taking up bandwidth with what me be a simple problem).  I will 
summarize all replies and submit them to the archives for a start to a 
CISCO tuning guide. 

I've included some of our CISCO parameters.  If you need to see 
anything else, just ask.

Thanks to all,

Signed...CLUE-LESS

Barry L. Greene

Internet  greenebl@PEOCU1.NAVY.MIL


======================================================================
                            CISCO Configuration Info
======================================================================

sh ver
GS Software (GS2-BRX), Version 8.1(19)
Copyright (c) 1986-1990 by cisco Systems, Inc.
Compiled Mon 06-Aug-90 02:30

System Bootstrap, Version 4.2(4)

PEOCU-GW uptime is 20 hours, 58 minutes
System restarted by power-on
Running default software

CSC2 (68020) processor with 1024K bytes of memory.
X.25 software.
Bridging software.
1 MCI controller.
1 Ethernet/IEEE 802.3 interface.
1 Serial network interface.
32K bytes of non-volatile configuration memory.
Configuration register is 0x301




PEOCU-GW#sh interface

Ethernet 0 is up, line protocol is up
  Hardware type is MCI Ethernet, hardware address is 0000.0C00.66A8
  Internet address is 192.73.215.2, subnet mask is 255.255.255.0
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 
1/255
  Encapsulation is ARPA, loopback is not set, keepalive is set (10 
sec.)
  ARP type: ARPA, HP-PROBE
  Last input 0:00:00, output 0:00:01, output hang never
  Output queue 0/100, 0 drops; input queue 0/75, 0 drops
  Five minute input rate 397 bits/sec, 2 packets/sec
  Five minute output rate 297 bits/sec, 1 packets/sec
     21477 packets input, 2734606 bytes, 0 no buffer
     Received 5998 broadcasts, 0 runts, 0 giants
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     13877 packets output, 1959430 bytes
     0 output errors, 1 collisions, 0 interface resets, 0 restarts
Serial 0 is up, line protocol is up
  Hardware type is MCI Serial
  Internet address is 26.14.0.67, subnet mask is 255.0.0.0
  MTU 1006 bytes, BW 56 Kbit, DLY 20000 usec, rely 222/255, load 1/255
  Encapsulation is DDNX25, loopback is not set
  LAPB state is CONNECT, T1 3000, N1 8232, N2 20, K 7
      VS 7, VR 2, RCNT 0, Remote VR 7, Retransmissions 0
      IFRAMEs 13161/14975 RNRs 0/0 REJs 0/2534 SABMs 12/0 FRMRs 0/0 
DISCs 0/0
  X25 address 000000671400, state R1, modulo 8, idle 0, timer 0, nvc 2
      Window size: input 2, output 2, Packet size: input 128, output 
128
      Timers: T20 180 T21 200 T22 180 T23 180 TH 0
      Channels: Incoming 1-64 Two-way 1-64 Outgoing 1-64
      RESTARTs 9/0 CALLs 212+0/85+0/0+0 DIAGs 0/0
  Last input 0:00:30, output 0:00:01, output hang never
  Output queue max 100, 0 drops; input queue 0/100, 0 drops
  Five minute input rate 175 bits/sec, 0 packets/sec
  Five minute output rate 180 bits/sec, 0 packets/sec
     46401 packets input, 1328409 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants
     22 input errors, 9 CRC, 14 frame, 0 overrun, 0 ignored, 6 abort
     56968 packets output, 1280912 bytes
     0 output errors, 0 collisions, 8 interface resets, 0 restarts
     1 carrier transitions


PEOCU-GW# sh protocol

Global values:
  Internet Protocol routing is enabled
Ethernet 0 is up, line protocol is up
  Internet address is 192.73.215.2, subnet mask is 255.255.255.0
Serial 0 is up, line protocol is up
  Internet address is 26.14.0.67, subnet mask is 255.0.0.0


PEOCU-GW#sh tcp


tty2, virtual tty from host 192.73.215.5
Connection state is ESTAB, I/O status: 1, unread input bytes: 1
Local host: 192.73.215.2, 23   Foreign host: 192.73.215.5, 2425

Enqueued packets for retransmit: 0, input: 0, saved: 0

Event Timers (current time is 75579872):
Timer:       Retrans   TimeWait    AckHold    SendWnd  KeepAlive
Starts:           58          0         77          0          0 
Wakeups:           0          0         20          0          0 
Next:              0          0   75580136          0          0 

iss:   75481344  snduna:   75484486  sndnxt:   75485022     sndwnd:   
3018
irs:  378905117  rcvnxt:  378905212  rcvwnd:       2144  delrcvwnd:     
94

SRTT: 300 ms, RTTO: 607 ms, RTV: 3 ms, KRTT: 0 ms
minRTT: 8 ms, maxRTT: 548 ms, ACK hold: 300 ms
Flags: passive open

Datagrams (max data segment is 536 bytes):
Rcvd: 137 (out of order: 0), with data: 78, total data bytes: 94
Sent: 84 (retransmit: 0), with data: 63, total data bytes: 3681
PEOCU-GW#
======================================================================
==========

bruce@ccavax.camb.com (Barton F. Bruce) (12/22/90)

In article <31096@boulder.Colorado.EDU>, GREENEBL@PEOCU1.NAVY.MIL (BARRY) writes:

> 6210s).  Our link with the Internet (MILnet to be exact) is a 19.2 

>   MTU 1006 bytes, BW 56 Kbit, DLY 20000 usec, rely 222/255, load 1/255

Try setting your serial line port to the actual line speed. (56kb .ne. 19.2kb)