16 Sep
2015
16 Sep
'15
1:34 p.m.
Sampsa Laine <sampsa at mac.com> writes:
On 16 Sep 2015, at 11:46, Brian Schenkenberger, VAXman-
=
<system at TMESIS.COM> wrote:
/ITEM=3DOPERATION_RATE.
It's a performance metric that is maintained in/by VMS about the number of I/O
operations to the disks. Maintaining block counts would be more/only meaning-
ful on a per-disk basis. That's generally not something that's a performance
metric.
This is a very simple procedure to get you a block/second count. Put this in
a file (BLOCKS_PER_SECOND.COM, for example) and execute it with the disk name
in question. (ie. $ @BLOCKS_PER_SECOND DKA100)
$ 100$: BLOCKS_THEN = F$getdvi(P1,"FREEBLOCKS")
$ WAIT ::01
$ WRITE SYS$OUTPUT BLOCKS_THEN-F$getdvi(P1,"FREEBLOCKS") ! THEN - NOW
$ GOTO 100$
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Sampsa Laine <sampsa at mac.com> writes:
=20
> I'm running a batch job that is creating a large (82 GB) file and =3D
> monitoring the system with MONITOR DISK.
>=20
> The value I'm getting is 39 - what does this actually mean, what is =
the
=3D
unit that
is being monitored?
=20
=20
I'm assuming you did not specify /ITEM. =46rom the MONITOR HELP:
=20
When the /ITEM qualifier is omitted, the default is = :
:
OPERATION_ Specifies that I/O operation rate statistics are
RATE displayed for each disk.
=20
What's you concern, if any?
Yes, I did this but the operation rate does not give me an indication of =
how many block/second are beyond read/written, or does it? 
1:46 p.m.
On 2015-09-16 13:34, Brian Schenkenberger, VAXman- wrote:
Sampsa Laine <sampsa at mac.com> writes:
Wouldn't that just show a delta of how many blocks have been allocated?
That do not really correspond to I/O throughput.
That said, what does the monitor operation_rate tell? Is it QIOs, disk
blocks, disk requests, or something else?
If it would actually be disk blocks, then Sampsa can indeed deduce I/O
rates from it, since we know the size of a disk block.
However, QIOs can cover many disk blocks, and so can I/O requests.
While I'm at it - a slightly different question. On a VMS system (VMS
7.3 on a VAX), I now have like hundreds of telnet connections that are
in a SUSP state. This have gone so far that I cannot establish any more
connections to the system. I have no idea what people/probes/robots have
been doing, but it seems TCP/IP or telnet daemon in VMS 7.3 have some
issues.
But my first question is, how do I get rid of all these processes? Do I
have to kill each one, giving the PID, or is there some better way of
getting this unstuck?
Johnny
On 16 Sep 2015, at 11:46, Brian Schenkenberger,
VAXman- =
<system at TMESIS.COM> wrote:
/ITEM=3DOPERATION_RATE.
It's a performance metric that is maintained in/by VMS about the number of I/O
operations to the disks. Maintaining block counts would be more/only meaning-
ful on a per-disk basis. That's generally not something that's a performance
metric.
This is a very simple procedure to get you a block/second count. Put this in
a file (BLOCKS_PER_SECOND.COM, for example) and execute it with the disk name
in question. (ie. $ @BLOCKS_PER_SECOND DKA100)
$ 100$: BLOCKS_THEN = F$getdvi(P1,"FREEBLOCKS")
$ WAIT ::01
$ WRITE SYS$OUTPUT BLOCKS_THEN-F$getdvi(P1,"FREEBLOCKS") ! THEN - NOW
$ GOTO 100$ Sampsa Laine <sampsa at mac.com> writes:
=20
> I'm running a batch job that is creating a large (82 GB) file and =3D
> monitoring the system with MONITOR DISK.
> =20
> The value I'm getting is 39 - what does this actually mean, what is =
the
=3D
unit that
is being monitored?
=20
=20
I'm assuming you did not specify /ITEM. =46rom the MONITOR HELP:
=20
When the /ITEM qualifier is omitted, the default is = :
:
OPERATION_ Specifies that I/O operation rate statistics are
RATE displayed for each disk.
=20
What's you concern, if any?
Yes, I did this but the operation rate does not give me an indication of =
how many block/second are beyond read/written, or does it? 
1:53 p.m.
You're probably under a Chinese/Russian robot attack, trying to brute-force their way
in.
I've had this on occasion and am tempted to just drop all packets originating from
China..
Not sure what the best way to do this is, I have a pretty simple consumer level router
(Draytek) so I guess I could use iptables or something on Linux - however I'm not if
that'll just affect the host I run the iptables command on or the whole interface.
Basically, I have one physical interface for 8 virtual machines and a bunch of SIMH
instances etc. If I could drop the packets at the interface of the host machine it'd
be ideal.
Any iptables experts out there?
sampsa
On 16 Sep 2015, at 12:46, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-09-16 13:34, Brian Schenkenberger, VAXman-
wrote:
Sampsa Laine <sampsa at mac.com> writes:
Wouldn't that just show a delta of how many blocks have been allocated? That do not
really correspond to I/O throughput.
That said, what does the monitor operation_rate tell? Is it QIOs, disk blocks, disk
requests, or something else?
If it would actually be disk blocks, then Sampsa can indeed deduce I/O rates from it,
since we know the size of a disk block.
However, QIOs can cover many disk blocks, and so can I/O requests.
While I'm at it - a slightly different question. On a VMS system (VMS 7.3 on a VAX),
I now have like hundreds of telnet connections that are in a SUSP state. This have gone so
far that I cannot establish any more connections to the system. I have no idea what
people/probes/robots have been doing, but it seems TCP/IP or telnet daemon in VMS 7.3 have
some issues.
But my first question is, how do I get rid of all these processes? Do I have to kill each
one, giving the PID, or is there some better way of getting this unstuck?
Johnny
On 16 Sep 2015, at 11:46, Brian Schenkenberger,
VAXman- =
<system at TMESIS.COM> wrote:
It's a performance metric that is maintained in/by VMS about the number of I/O
operations to the disks. Maintaining block counts would be more/only meaning-
ful on a per-disk basis. That's generally not something that's a performance
metric.
This is a very simple procedure to get you a block/second count. Put this in
a file (BLOCKS_PER_SECOND.COM, for example) and execute it with the disk name
in question. (ie. $ @BLOCKS_PER_SECOND DKA100)
$ 100$: BLOCKS_THEN = F$getdvi(P1,"FREEBLOCKS")
$ WAIT ::01
$ WRITE SYS$OUTPUT BLOCKS_THEN-F$getdvi(P1,"FREEBLOCKS") ! THEN - NOW
$ GOTO 100$ Sampsa Laine <sampsa at mac.com> writes:
=20
> I'm running a batch job that is creating a large (82 GB) file and =3D
> monitoring the system with MONITOR DISK.
> =20
> The value I'm getting is 39 - what does this actually mean, what is =
the
=3D
> unit that is being monitored?
=20
=20
I'm assuming you did not specify /ITEM. =46rom the MONITOR HELP:
=20
When the /ITEM qualifier is omitted, the default is =
/ITEM=3DOPERATION_RATE.
:
:
OPERATION_ Specifies that I/O operation rate statistics are
RATE displayed for each disk.
=20
What's you concern, if any?
Yes, I did this but the operation rate does not give me an indication of =
how many block/second are beyond read/written, or does it?
1:58 p.m.
On 2015-09-16 13:53, Sampsa Laine wrote:
You're probably under a Chinese/Russian robot
attack, trying to brute-force their way in.
Quite possibly. Some day I should summarize and post logs of attempts at
Madame.Update.UU.SE (RSX). It's quite funny. Fortunately, my RSX
implementation is rather robust.
I've had this on occasion and am tempted to just
drop all packets originating from China..
Not sure what the best way to do this is, I have a pretty simple consumer level router
(Draytek) so I guess I could use iptables or something on Linux - however I'm not if
that'll just affect the host I run the iptables command on or the whole interface.
Basically, I have one physical interface for 8 virtual machines and a bunch of SIMH
instances etc. If I could drop the packets at the interface of the host machine it'd
be ideal.
Any iptables experts out there?
I know how iptables and similar tools work. That is no help here.
This is a *VAX* running VMS. Not some simh instance...
Johnny
sampsa
On 16 Sep 2015, at 12:46, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-09-16 13:34, Brian Schenkenberger,
VAXman- wrote:
Sampsa Laine <sampsa at mac.com> writes:
Wouldn't that just show a delta of how many blocks have been allocated? That do not
really correspond to I/O throughput.
That said, what does the monitor operation_rate tell? Is it QIOs, disk blocks, disk
requests, or something else?
If it would actually be disk blocks, then Sampsa can indeed deduce I/O rates from it,
since we know the size of a disk block.
However, QIOs can cover many disk blocks, and so can I/O requests.
While I'm at it - a slightly different question. On a VMS system (VMS 7.3 on a VAX),
I now have like hundreds of telnet connections that are in a SUSP state. This have gone so
far that I cannot establish any more connections to the system. I have no idea what
people/probes/robots have been doing, but it seems TCP/IP or telnet daemon in VMS 7.3 have
some issues.
But my first question is, how do I get rid of all these processes? Do I have to kill each
one, giving the PID, or is there some better way of getting this unstuck?
Johnny
On 16 Sep 2015, at 11:46, Brian Schenkenberger,
VAXman- =
<system at TMESIS.COM> wrote:
> Sampsa Laine <sampsa at mac.com> writes:
> =20
>> I'm running a batch job that is creating a large (82 GB) file and =3D
>> monitoring the system with MONITOR DISK.
>> =20
>> The value I'm getting is 39 - what does this actually mean, what is =
the =3D
>> unit that is being monitored?
> =20
> =20
> I'm assuming you did not specify /ITEM. =46rom the MONITOR HELP:
> =20
> When the /ITEM qualifier is omitted, the default is =
/ITEM=3DOPERATION_RATE.
> :
> :
> OPERATION_ Specifies that I/O operation rate statistics are
> RATE displayed for each disk.
> =20
> What's you concern, if any?
Yes, I did this but the operation rate does not give me an indication of =
how many block/second are beyond read/written, or does it?
It's a performance metric that is maintained in/by VMS about the number of I/O
operations to the disks. Maintaining block counts would be more/only meaning-
ful on a per-disk basis. That's generally not something that's a performance
metric.
This is a very simple procedure to get you a block/second count. Put this in
a file (BLOCKS_PER_SECOND.COM, for example) and execute it with the disk name
in question. (ie. $ @BLOCKS_PER_SECOND DKA100)
$ 100$: BLOCKS_THEN = F$getdvi(P1,"FREEBLOCKS")
$ WAIT ::01
$ WRITE SYS$OUTPUT BLOCKS_THEN-F$getdvi(P1,"FREEBLOCKS") ! THEN - NOW
$ GOTO 100$
2:04 p.m.
On 16 Sep 2015, at 12:58, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-09-16 13:53, Sampsa Laine wrote:
You're probably under a Chinese/Russian robot
attack, trying to brute-force their way in.
Quite possibly. Some day I should summarize and post logs of attempts at
Madame.Update.UU.SE (RSX). It's quite funny. Fortunately, my RSX implementation is
rather robust.
I know how iptables and similar tools work. That is no
help here.
This is a *VAX* running VMS. Not some simh instance...
My bad, I assumed you were running SIMH, sorry.
One solution is to set up a Linux box that drops say all packets from China and then uses
socat to forward the ports you want to the actual VAX.
4:01 p.m.
On 2015-09-16 14:04, Sampsa Laine wrote:
On 16 Sep 2015, at 12:58, Johnny Billquist <bqt at softjar.se> wrote:
Which still requires that I would be sitting on an internal network with
a router I have control over, in which case, why would I use socat? This
setup would mean I have routing running on the Linux box, and I can
filter what is being routed more easily just directly on the box without
involving socat.
But this would also require that I have a separate network for this
setup. We're talking about a machine that are on the internet today...
On a well known, static ip address.
Johnny
On 2015-09-16 13:53, Sampsa Laine wrote:
You're probably under a Chinese/Russian robot
attack, trying to brute-force their way in.
Quite possibly. Some day I should summarize and post logs of attempts at
Madame.Update.UU.SE (RSX). It's quite funny. Fortunately, my RSX implementation is
rather robust.
I know how iptables and similar tools work. That
is no help here.
This is a *VAX* running VMS. Not some simh instance...
My bad, I assumed you were running SIMH, sorry.
One solution is to set up a Linux box that drops say all packets from China and then uses
socat to forward the ports you want to the actual VAX.
4:03 p.m.
On 16 Sep 2015, at 15:01, Johnny Billquist <bqt at softjar.se> wrote:
But this would also require that I have a separate network for this setup. We're
talking about a machine that are on the internet today... On a well known, static ip
address.
Then you're unfortunately pretty out of luck unless - AFAIK VMS doesn't have
anything like iptables to help you filter out the connections.
A really crappy solution would be to restart the IP stack every so often but there are of
course issues with that as well..
sampsa
4:07 p.m.
On 2015-09-16 16:03, Sampsa Laine wrote:
On 16 Sep 2015, at 15:01, Johnny Billquist <bqt at softjar.se> wrote:
Well, you are trying to suggest ways to prevent this from happening. And
no, VMS do not have iptables, as far as I know.
When you are looking for is essentially a way to block some ranges of
addresses. That can be done in a router, or sometimes switch. Quite
possible I'll look into that. But that don't answer my current question,
how to fix the current state on the VMS system. And no, I do not
consider "reboot" to be the solution. :-)
But this would also require that I have a separate network for this setup. We're
talking about a machine that are on the internet today... On a well known, static ip
address.
Then you're unfortunately pretty out of luck unless - AFAIK VMS doesn't have
anything like iptables to help you filter out the connections. A really crappy solution would be to restart the IP
stack every so often but there are of course issues with that as well..
Yeah... No... Not going there.
Johnny
17 Sep
17 Sep
12:36 a.m.
Quick fix though a bit ugly.. Shutdown the telnet daemon for a few seconds then restart
it. Ugly but effective and EASY!
-Steve
Sent from my iPhone
On Sep 16, 2015, at 10:07, Johnny Billquist <bqt at
softjar.se> wrote:
On 2015-09-16 16:03, Sampsa Laine wrote:
Well, you are trying to suggest ways to prevent this from happening. And no, VMS do not
have iptables, as far as I know.
When you are looking for is essentially a way to block some ranges of addresses. That can
be done in a router, or sometimes switch. Quite possible I'll look into that. But that
don't answer my current question, how to fix the current state on the VMS system. And
no, I do not consider "reboot" to be the solution. :-)
On 16 Sep 2015, at 15:01, Johnny Billquist
<bqt at softjar.se> wrote:
But this would also require that I have a separate network for this setup. We're
talking about a machine that are on the internet today... On a well known, static ip
address.
Then you're unfortunately pretty out of luck unless - AFAIK VMS doesn't have
anything like iptables to help you filter out the connections. A really crappy solution would be to restart the
IP stack every so often but there are of course issues with that as well..
Yeah... No... Not going there.
Johnny
3387
days inactive
3387
days old
9 comments
4 participants
participants (4)
-
bqt＠softjar.se -
sampsa＠mac.com -
steve＠davidson.net -
system＠TMESIS.COM