[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

384.0. "How to get events notified to the C3 interface" by WELTM1::CRIDDLE (Graham Criddle, MCS Tech Consultant, 853-4015) Thu Sep 01 1994 15:17

Hi,

I am configuring DCM 1.5 on OSF/1 V2 and am unable to get events to cause
any Icon colour change nor to appear in the events list.

Can anyone please point me in the right direction.

The details (for my test case are):

System Name         = WELCS2
    Information     =
    Connection      = LAT (terminal server)
    Terminal Server = TESTDS300
    Server Port     = PORT_8
    Terminal Device = /dev/tty0k
    Scan Profile    = OSI Network Scan
    Icon filename   = VAXstation_3100.xbm
    Console line    = Enabled
    Logging is enabled, directory = /var/opt/console/logs


Scan Name       = OSI Network Scan
    Information =
    Events (1)
      Link Halted
    Scans (0)

Event Name      = Link Halted
    Information =
    Class       =
    Subsystem   =
    Text        = Halted
    Text string = Literal (exact pattern match)
    Start       = 2
    Count       = 3
    Priority    = Major


I assumed that with the above set up, if the text string 'Halted' appeared in
the console output from node WELCS2, an icon colour change would take place
and the events would be updated.

I can connect into the console port from the WELCS2 icon (suggesting that the
comms stuff is working) and all the output which comes out of the port is 
being logged correctly.

Any thoughts?

Rgds,
Graham
T.RTitleUserPersonal
Name		DateLines
384.1OPG::PHILIPAnd through the square window...Thu Sep 01 1994 15:2614
Graham,

  The setup you have described will only allow the C3 icon
  colours to change.

  If you want to see an eventlist action routine with the
  events in, then you will have to start defining filters
  and dispatches.

  You did do a reconfigure after you added your event etc.
  didnt you?

Cheers,
Phil
384.2WELTM1::CRIDDLEGraham Criddle, MCS Tech Consultant, 853-4015Thu Sep 01 1994 16:1014
Hi, Phil..

Thanks for the reply.

Yes, I understand that for the action routines and so on I need to do some
more work.

What I don't understand is that with the configuration as described I don't
get any icon colour changes?

Am I right in thinking I should?

Rgds,
Graham
384.3OPG::PHILIPAnd through the square window...Thu Sep 01 1994 17:2918
Graham,

  Yes, you should get the C3 changing its icon color for that
  particular system, you should also get an event in the
  eventlist started with the C3.

  So, check the following...

	Is ENS running (do you have a console_ensd process)?

	If you connect in one window and monitor in another,
	does the monitor interface "see" an event?


Cheers,
Phil
384.4WELTM1::CRIDDLEGraham Criddle, MCS Tech Consultant, 853-4015Thu Sep 01 1994 17:4020
Hi, Phil.

Thanks again.

I do have a console_ensd process (in fact I have two!)

  508 ??  IW       0:00.21 /usr/bin/console_ensd
  637 p2  I        0:00.45 /usr/bin/console_ensd


If I connect to the console, and then monitor the interface an another window
then the monitor window sees the text string "Halted" which should cause
the event to fire (as I understand it)

The event history window for WELCS2 shows internal CMgr events but nothing else.

I'm confused!

Rgds,
Graham
384.5OPG::PHILIPAnd through the square window...Thu Sep 01 1994 17:4418
Graham,

  It looks like you have got yourself in a bit of a mess!!

  I suggest you do a console -s to shut the software down
  and then kill off any remaining console* processes, after
  you have done this, try starting console manager again
  (/sbin/console_startup or at least I think thats where
  the command is, if its not there, it'll be in /etc)

  You must use the console_startup script as it will clear
  out the directory we use for our temporary files.

  Let me know how you get on.

Cheers,
Phil
384.6WELTM1::CRIDDLEGraham Criddle, MCS Tech Consultant, 853-4015Fri Sep 02 1994 09:238
Hi, Phil

That did it.

Many thanks,

Rgds,
Graham