[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1022.0. "action script on PCM local event" by 48649::NEYROUD_N () Wed Oct 04 1995 13:02

    
    I would like to know if PCM can help me for the following application:
    
    
    On reception of local event, and from a script file I would like 
    to shutdown a remote system through console port to be sure that 
    the remote system will be always stopped.
    
    Thanks in advance,
    
    Nadine
T.RTitleUserPersonal
Name		DateLines
1022.160591::ELLISSAre you all sitting too comfybold square on your botty? - Then we'll beginThu Oct 05 1995 00:487
Nadine,

well, yes, you can. However, if the system needs a password to log in, to shut
it down cleanly, then you'll have to store th password in the script file, and
this is a real security 'no-no'.

Shaun
1022.2May I have more explanations?48649::NEYROUD_NThu Oct 05 1995 04:256
    If you could explain me a bit more what's kind of PCM mechanism I can
    use, I have PCM documentation on my desk.
    
    Thanks a lot,
    
    Nadine
1022.3CSC32::BUTTERWORTHGun Control is a steady hand.Mon Oct 09 1995 12:0431
    As long as you understand the security hole that Shaun pointed out
    then  here is your answer:
    
    Create a DIALOG file for use with the CONSOLE DIALOG command. This
    file will contain all the neccesary commands to send to the managed
    system to login to it and shut it down.
    
    Now you can create another command file that will actually run the DIALOG
    command for you. This command file will be whats known as an ENS action 
    routine. You must then use the PCM config editor to define it as
    an action routine within the PCM config file. 
    
    Now assuming you haven't defined the event in the config editor you
    need to do that  as well as include it in the scan profile for the
    system in question.
    
    The next step is to create a filter that will match only on this
    event. *MAKE SURE* that when you define the filter that you have
    deselected  "Filter all classes" . If you don't, every event that
    occurs will attempt to run the action routine and shut the system down.
    The filter is also that which points at the action routines to run when
    events occur so you must attach a dispatch record to te filter that 
    tells it to run your action routine.
    
    These are the basic steps. The manual outlines the details.
    
    Regs,
      Dan
    
    
     Buffer: NOTES$