Network monitor

[geir_2]

Hi,

Is there any utilities/commands I can use if I want find information about historic network traffic. I also wnat to find out why some process suddenly is generating huge amount of network traffic.

This morning I saw that the the network traffic suddenly exploded, and I want to find some information about the reason for it (process and packets on network).

I also want to get software for network and system managment. So if someone have some recommandadtion, it would be great.

regards geir

[Ian Miller.]

There is not a built in command that maintains a history of network counters. T4 can be used
(see http://h71000.www7.hp.com/OpenVMS/products/t4/index.html
)

There are other products also.

[Karl Rohwedder]

For online monitoring I often use ETHEREAL
(http://www.ethereal.com/).

mfg Kalle

[Wim Van den Wyngaert]

You can request an operator.log message for each activation of a service via
ucx set service xxx/log=activate

ucx show dev /fu can give you statistics of that connection (e.g. bytes transferred) but only during the time the line is used.

But some scripting is required to really do some monitoring.

Wim

[labadie_1]

It depends what you want to monitor. Tcp/IP is the most common, but Decnet phase IV, Decnet Osi, Lat or some less common protocols may be needed for your site.

For Decnet phase IV,
$ mc ncp sh known node counters
may show some response timeouts, this means that some trames were lost when talking between
your node and the node shown by the command.
see to
$ mc ncp sh exe counter
$ mc ncp sh k line counter

For Lat
$ mc latcp sh link/counter
can show various error code, see for example
http://pi-net.dyndns.org/docs/openvms0731/731final/6048/6048pro_038.html
search for
The following table lists and describes counters common to both CSMA/CD (carrier sense, multiple access with collision detect) and FDDI (Fiber Distributed Data Interface) links:

$ mc latcp sh node/counter

For Tcp/IP
do first
$ @ sys$startup:tcpip$define_commands

now you have the "standard" (in the unix World)
netstat, ifconfig, sysconfig...

so
$ netstat -i
$ netstat -m
$ netstat -s

$ sysconfig -q inet
$ sysconfig -q socket

[Ian Miller.]

All the commands given give a snapshot of the counters etc now but for a historical record you have to use these commands or others, collect the data in files and write something to display it. This has been done already in T4 (and may be other things).

[Daniel Fernandez Illan]

Also, you can check SYS$MANAGER:OPERATOR.LOG and search network's events.
If you need monitor a DECnet phase V you can use ncl counters
ncl>sho entity all counters
Best Regards.

[comarow]

Here's a great web site.
I wish I gave it sooner.
http://www.ethereal.com/

You can download several sniffer type tools.

Good luck.

Bob

[Uwe Zessin]

Scroll a bit up and you should see that Karl has mentioned it a few months ago:
Mar 14, 2005 10:33:47

[comarow]

Thanks, missed it.