| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4519.1 | Very Strange .. I'll check into it | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Wed Feb 10 1993 09:26 | 8 |
| Were you using the 'Developers Dictionary' ? Probably not - you were just
executing one of the demo scripts and not adding any of your own custom
scripts - Right ?
Also - what was the exact 'Script Command' that you were using in the
script create directive ?
/keith
|
| 4519.2 | using the mcc supplied scripts | HERON::PATEL_A | LoLo-AQIC-I82Q-B4IP, - LMF | Wed Feb 17 1993 08:39 | 8 |
| sorry for the delays, your assumptions are correct. the command I use
for both is the same
I register a script to do memory test from the tool box for the local
system - works, the same script with the proxy etc set up same command
during registration causes the failiure
Amrit
|
| 4519.3 | I cannot reproduce this problem | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Wed Feb 17 1993 11:53 | 39 |
| Amrit,
I just tried using both the FCL and Iconic Map to execute the Memory script.
The FCL command was:
create script keith memory local-system -
command = "@mcc_scripts:mcc_memory"
I executed the script (Show all status) and it worked.
I then made a script which would execute remotely .. the FCL command was:
create script keith memory remote-molar -
command = "@mcc_scripts:mcc_memory molar"
Because this is a remotely executing script, I had to setup the remote
system (MOLAR) first:
o In Authorize I added network proxy for myself:
UAF> add/proxy nanovx::roberts roberts/default
o I defined a system logical to say where the mcc_memory script was:
def/sys/exe mcc_memory mcc_scripts:mcc_memory.com
Then, from my local system (NANOVX) I executed the 'remote-molar' script.
I enabled opcom and saw a subprocess get started. This subprocess was
executing the 'mcc_memory' script on my local system. Then, a network
process started on the remote system, MOLAR. The network process was
executing the mcc_memory script on the remote system. Then, I got the
output of the remotely executing script.
I tried this with both FCL and the Iconic Map.
Are these the steps you tried ?
/keith
|
| 4519.4 | LOOSELY INTEGRATED SCRIPT EXAMPLES??? | IOOSRV::GALVIN | Mic, (306) 781-5448 | Mon May 31 1993 19:10 | 26 |
| Keith,
I've been doing some work with the SCRIPT AM as well... I want to
use the IMPM exclusively, and want to eventually write ALARM rules. I
have the MCC_MEMORY.COM down, now; what would be the syntax(from IMPM)
to do the same remote activities for MCC_DISK, MCC_SYSGEN,
MCC_DIRECTORY, and could you provide an example of how to use the
COMMAND child entity within the IMPM?
I am trying to use the LOOSELY integrated scripts and have to
eventually monitor/alarm PDP systems...
This is somewhat critical (aren't they always?) We're trying to show a
proof of concept to a large DEC client in Canada...
Can you also talk about the correlation between the SCRIPT & COLLECTOR?
The platform I'm working on is VMS 5.5-2, DECnet V, BMS 1.3
thanks,
/Mic
PS I've got a "panick ridden" note at the end of this conference as
well...
|
| 4519.5 | Not all the example scripts operate remotely .. 8( | MOLAR::ROBERTS | Keith Roberts - Network Management Applications | Tue Jun 01 1993 11:40 | 36 |
| re: .4
> I've been doing some work with the SCRIPT AM as well... I want to
> use the IMPM exclusively, and want to eventually write ALARM rules. I
> have the MCC_MEMORY.COM down, now; what would be the syntax(from IMPM)
> to do the same remote activities for MCC_DISK, MCC_SYSGEN,
> MCC_DIRECTORY, and could you provide an example of how to use the
> COMMAND child entity within the IMPM?
The MCC_MEMORY and MCC_SYSGEN scripts were written to execute remotly;
The MCC_DISK and MCC_DIRECTORY scripts were not .. it should be pretty
easy to adapt any script to execute remotely.
Using the COMMAND child entity is just like any other Script child entity.
You click on COMMAND and give the script a name. Then you fill out the
form (description, command, timeout, category) .. for a Command I used:
show time
When I executed the script (show status) 'show time' executed and I was
returned 'arg1 = 10:26:33' .. not that the first argument from 'show time'
is the date .. this was mapped to the output entity and does not appear
as an attribute. Ok?
> Can you also talk about the correlation between the SCRIPT & COLLECTOR?
Both techniques allow you to get data into DECmcc without the need of
writing C source code:
o The Script AM gets Attributes into DECmcc, and
o the Data Collector gets Events into DECmcc
Hope this helps.
/keith
|