|
For this release, we didnt have time for full
integration, however, in the OSF/1 kit we are
about to announce, there is some rudimentary
integration which will allow you to connect
to consoles etc from the Netview interface.
Its on our list to perform a tighter integration
in a future Console Manager release.
Cheers,
Phil
|
| Hi Greg,
I am also hoping for some good stuff from the PNV people to
make eventing easier for applications which do not use SNMP as all
Netview really understands is SNMP traps for events, and that will be
rather difficult to impliment in the way we do eventing in PCM.
If you have specific requirements from customers please do let us know
( we are near Phase 0 for the next version ) as all such input is
valuable.
Cheers Simon....
|
| Simon,
just thought you ought to know that PNV, with the DECnet kit, is also
going to be able to understand mcc events. There is a discussion on
this in the PSW conference (Or it may be the POLYCENTER conference).
Martin
|
| PNV actually has a function similar to MCC_SEND_EVENT.EXE but you have to
execute it on the PNV machine.
So to do this you need the following:
1/ UCX installed and configured on your VMS machine
2/ An account on your OSF/1 machine
3/ "proxy" set up between your VMS username and the user on OSF/1
4/ An action routine that makes a remote shell command to the OSF/1
machine.
I did this to transfer events from PSW to PNV during the 8'th of February
announcement. It should be possible to use tha same thing for PCM.
I used some different commandprocedures for different events in PSW. They
generate different Severitys to PNV.
I used the following commandprocedure as action routine for "critical" events.
STKMCC2 is the machine with PNV installed on it, and my user on that machine
is bystam.
$! --- SEND_TO_PNV_CRITICAL.COM file ---
$!
$! Intends:
$! --------
$!
$! PSW 1.0 action routine to trigger in case you want PSW to take action
$! on stopped queues.
$!
$! Parameters passed by PSW to this command procedure when triggering it:
$! ----------------------------------------------------------------------
$!
$! p1 : Message text as it is displayed on PSW screen.
$! p2 : PSW Message date & time stamp.
$! p3 : Short event code describing the message type.
$! p4 : Checked node name.
$! p5 : Cluster name.
$! p6 : Action routine name.
$! p7 : Message type ("SNS_C_NEW" if new, "SNS_C_UPD " if updated).
$!
$! Some of thos parameters are used by this procedure to try and start
$! the queues.
$! (see example given below)
$!
$! Set up requirements before using this procedure:
$! ------------------------------------------------
$!
$! _ PSW side
$! ----------
$!
$! + Assumed that this command file name is MINICALL.COM
$! (If you've changed its name, please replace it also in that memo...)
$! + Assumed that START_QUEUES is in your_directory.
$! + Assumed that PSW profile exists...
$!
$! _ Create the action routine, for instance named MINICALL, within PSW:
$!
$! SNS> ADD PROFILE/ACTION_ROUTINE/SET=MINICALL
$!
$! Answer to the subsequent questions:
$! USERNAME : your_name or SYSTEM
$! Procedure name : SYS$ELSEWHERE:[ISMANAGER.IS_BYSTAM]MINICALL.COM
$! Batch queue name: SYS$BATCH
$!
$! _ Assign the MINICALL action routine to the node you wan't to
$! monitor.
$!
$! SNS> MOD PROFILE/CLASS=MINICALL
$!
$! Use arrows and select keys to correlate the MINICALL action routine
$! with the events you wan't
$!
$! - Check that the genuine node(s) are assigned to the class QUEUES
$!
$! SNS> SHOW PROFILE/NODE=your_node
$! and eventually :
$! SNS> MOD PROFILE/NODE=your_node/WITH_CLASS=MINICALL
$! or
$! SNS> ADD PROFILE/NODE=your_node/WITH_CLASS=MINICALL
$!
$! - Check the "Routine swich" (must be ON) in the PSW parameters list.
$!
$! SNS> MOD PROFILE/PARAMETER
$!
$!------------------------------------------------------------------------------
$!
$ Severity := FERR_EV
$ p7 = f$edit (p7,"collapse,upcase")
$ if "''p7'".eqs."SNS_C_REM" then $ Severity := NUP_EV
$!
$ p1 = f$edit (p1,"compress")
$ text = f$element (3," ",p1)
$ pos = f$locate (text,p1)
$ string = f$extract (pos,f$length(p1)-pos,p1)
$!
$ EVENT_CODE_ABBREV = P3 - "SNS_C_"
$ EVENT_TITLE = "''p3'"
$ EVENT_TEXT = "''p1'"
$ node = f$edit("''p4'","LOWECASE") + ".soo.dec.com"
$!
$ write sys$output "Destination: STKMCC2"
$ write sys$output "Event Title: ''event_title'"
$ write sys$output "Node : ''node'"
$ write sys$output "Event Text : ''event_text'"
$!
$ event = "/usr/OV/bin/event -u'stkmcc2' -h"+"'"+"''node'"+"'"+ -
" -s'a' -e"+"'"+"''Severity'"+"'"+" -d"+"'"+ -
" ''event_title' ''event_text'"+"'"
$ set ver
$ rsh stkmcc2/user="bystam" "''event'"
$ set nover
$!
$ exit
The Severity codes to PNV can be a lot of different things but you can start
by using the following:
Fatal Error: $ Severity := FERR_EV
Node_up (roughly equal to Clear) $ Severity := NUP_EV
Error: $ Severity := ERR_EV
Warning: $ Severity := WARN_EV
Node Down: $ Severity := NDWN_EV
You can get all the errorcodes from the /usr/OV/bin/event command by giving a
switch that I don't remember but it is in the help part that you get with -h.
I hope this helps somebody.
/Stefan
|