Re: VAX network extremely slow

On 10 maio, 11:32, "Richard Brodie" <R.Bro...@xxxxxxxx> wrote:
"valdemirs" <valdem...@xxxxxxxxx> wrote in message

news:9ca5c9fd-114a-4cea-9959-9fd24ce17204@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Pinging from my PC to a VAX I´m getting 42% packet loss.
Can you help me to solve this issue ?

Most likely you have some faulty hardware somewhere.

Map out your network, try PINGs from and to other combinations
of nodes and identify the common hardware.

"mc ncp show known lines count" may be helpful looking at what the
local connection to the VAX looks like. If you have managed switches
in the bad path, look see what their counters say. If you have cheap
commodity network hardware consider power cycling and/or replacing
it.

Please look at ncp sh kn lines count command´s output below:


svax5> mc ncp show known lines count


Known Line Counters as of 10-MAY-2010 11:35:37

Line = ISA-0

>65534 Seconds since last zeroed
3705420 Data blocks received
3693836 Multicast blocks received
0 Receive failure
245385831 Bytes received
244734875 Multicast bytes received
0 Data overrun
23340 Data blocks sent
13777 Multicast blocks sent
3384 Blocks sent, multiple collisions
4044 Blocks sent, single collision
1505 Blocks sent, initially deferred
1512059 Bytes sent
682784 Multicast bytes sent
2373 Send failure, including:
Excessive collisions
Carrier check failed
411 Collision detect check failure
0 Unrecognized frame destination
3 System buffer unavailable
0 User buffer unavailable
.

Relevant Pages

  • Re: VAX network extremely slow
    ... Most likely you have some faulty hardware somewhere. ... Map out your network, try PINGs from and to other combinations ... 3693836 Multicast blocks received ... 3384 Blocks sent, multiple collisions ...
    (comp.os.vms)
  • Re: General
    ... Their goal is going to be to sell as much hardware as possible, ... It sounds to me like there is a problem with the ROM update for your ... stuff that interacts with network adapters on your PC. ...
    (microsoft.public.pocketpc.activesync)
  • Re: Wikileaks, secondary effects
    ... Those last people are not in the business of security, ... local to network storage for documents and applications. ... Most workstations have no real need to attach peripherals aside from mouse and keyboard and since the lifetime of a desktop is about three years, "damaging" hardware to make it more secure is not a big deal. ... The professor who owned the project was under the fond illusion that if he just got all the static timing right, then all the bugs were *gone* This guy and many others in the 1980s and early '90s didn't grasp the complexity of a CPU or an OS and that the only way to wring bugs out is by users finding them. ...
    (sci.military.naval)
  • Re: Your favorite 10 analog ICs
    ... > engineers were Ham radio guys and seemed to think that measuring 60 Hz ... nationwide buildout plan for Ricochet 2 -- they ran out of money. ... they spent way too much on network hardware. ...
    (sci.electronics.design)
  • Re: File Transfer conundrum
    ... A week later I would call them back and I would set up a schedule so in case of network issues I would have our hardware type there to look at the line to see what the issue was. ... The sysprog would think they were the expert and go off on their own and set up the JES2 parms or VTAM mode table. ... The "other" quite minor issue was the program that sent and received the the data was an IBM FDP. ...
    (bit.listserv.ibm-main)