Conference csc32::consolemanager

    Rae, 
    
    I know this is a tall order but we need all the ALphastations and
    AlphaServers. Chances are we can just create 1 for each family, ie
    ALphastation/Server 1000  that would encompass the different processor
    speeds as thereis no difference in the console subsystems between say
    a 4/200 and a 4/250.
    
    Regs,
      Dan

Rae

Please take this reply seriously! I apologise for the length of the list, but
you did ask, and it would be nice if it ever came about. One of these days I may
get the time to go through console logs and pick out what I can, but time is not
in large supply. I tried to go through the scans in the shared directory
recently to get them into some sort of order, but nearly went mad.

We are an MCS group managing the largest Digital datacentre in the Southern
Hemisphere (Digital equipment - it doesn't belong to Digital). We are a
reference site for POLYCENTER, and it has crossed our minds that separate scans
for the following would be appropriate:

			VAX 3100, 4xxx, 7xxx
			Alpha 3000, 2100, 7000, 8200, 8400
			HS111, HS121
			HSD30, HSJ40
			DS900
			TL810, TL820

			VMS (updated constantly)
			Connection Manager
			Audit Server
			TCP/IP Services
			DECnet/OSI
			DCPS
			PrintServers
			PathWorks (various)
			LMF
			Scheduler
			Digital Unix
			DEC NSR
			...

Seriously, we have most of this stuff. We still use the VAX7000 scan on 8400s
simply bacause we don't know what else to do...

Hope this helps

Tony Sherrard

Assume we need all hardware/software scan for digital products and maybe for 3rd
party hard/soft.

Make it a sense to ask to engineering hard/soft to provide scans within
delivering a new product/version ?

Regards.
JF

Digital UNIX
Alpha 2100's
Alpha 1000's
Alpha 8400's
POLYCENTER Networker Save & Restore
POLYCENTER Scheduler V3.0
SAP R3
HSZ StorageWorks Controllers
SUN Sparc Stations
Gigaswitch
CISCO Routers

This is for Optus Vision, a cable TV Company in Australia. You've already got
the requirements for the parent company

    Hi,
    
    we need also scan profile for IBM-AIX, HP-UX systems and SUN-OS/Solaris.
    
    Regards

    
    
    
    
    Thank you all thusfar for your inputs.  Please keep the lists
    coming.
    
    RE: .2
    
    Tony: 
    
    Regarding your comment:
    "I tried to go through the scans in the shared directory recently 
    to get them into some sort of order, but nearly went mad."
    
    Can you explain?  It sounds to me that, even if the scan profiles
    were provided, it would still be a problem for you because of
    the way they are delivered/packaged/?????  Please elaborate on
    what it is that's causing you problems (aside from the lack of
    the scan profiles themselves) and propose an idea of what you'd
    like to see done here.
    
    And yes I intend to take this request seriously, and do what I can
    do to get this committed to by engineering management.
    
    RE: .3
    
    JF: 
    
    >Assume we need all hardware/software scan for digital products and
    >maybe for 3rd party hard/soft.
    
    I am assuming this, but would appreciate exact names of products
    that are needed.  This way I can at least submit the list with some
    reasonable priority, so that the ones that are the most needed get
    done first.
    
    >Make it a sense to ask to engineering hard/soft to provide scans within
    >delivering a new product/version ?
    
    We tried to do this, and will continue to try.  We've not been very
    successful in the past though, thus the lack of a decent/updated
    profiles library.  At times service delivery consultants have taken
    it upon themselves to develop these for us (thanks Shaun!), but very
    few product engineering groups have been able to help us out by
    providing the profiles for their products.  We've also tapped into
    the IM&T groups to see what they've done for their individual 
    facilities, and have received some scans in return.
    
    
    

         Rae

         Can I explain? I hope so. I need to add here, though, that I
         have no wish to denigrate the work of others; others'
         contributions have been extremely useful to us.

         We have a fairly wide range of managed systems which leads to
         a large event population. I'm sure we're all aware of the
         different ways this could be managed: the easiest would be to
         have one huge scan containing all events and to configure all
         systems with this scan (this did cross the mind), but my
         manager would complain at the 8412 needed to run it; the most
         difficult would be to have a scan for each managed system
         that is full of nothing but the events that may be seen on
         that system. I got a distinct feeling that some of the scans
         in your directory were of this sort.

         The best solution is to have scans for closely related
         events: one for VMS, one for Unix, one for VAX 7000, one for
         Alpha 7000 etc. Each system scan would contain nothing but
         scans that pertained to the system (for instance VAX 7000,
         VMS, DCPS, Security and CNXMAN). The one for VMS, for example
         - this applies to all scans, would contain events for all
         VMS, not just the latest version, so I could configure a
         system's scan to include the VMS scan and it wouldn't matter
         if it were running v1.0 or v7.0, if it bugchecked (or is that
         BUGCHECK, or perhaps BugCheck...) I would be notified; and I
         wouldn't have to remember to change the scans in the managed
         system's scan each time I upgraded the software. The extra
         events that would have to be checked would be minimal - it
         might even help the engineering groups to keep their messages
         the same. We need to be careful, however, to keep event names
         unique across the board...

         And this is what I was trying to do when I went mad.

         (And while you're listening, can we have nested groups and
         index numbers in system configuration so I can have some
         control over which control process controls which system,
         please)

         Tony Sherrard

Hi,

In my eyes, scan profiles should be constructed per layered product,
type of hardware, type of oprating system ect.

A scan profile should handle the collection of messages addressing a
piece of HW, a layered product, a operating system.
The final scan profile for a system then should be constructed as collection of
the "base" scanprofiles as below. BRSADV is a OpenVMS V6 cluster member,
DOMUS is a standalone OpenVMS V5 system. 


PCM Edit>
PCM Edit> sh system BRSADV
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
System Name         = BRSADV
    Information     = KETJE system: VAX 7000-710
    Connection      = LAT (terminal server)
    Terminal Server = BRASDV
    Server Port     = CRSTD1
    Scan Profile    = SCAN$BRSADV
    Icon filename   = VAX_7000.XBM
    Console line    = Enabled
    Logging is enabled, directory = CONSOLE$LOGFILES
PCM Edit>
PCM Edit>
PCM Edit>
PCM Edit>
PCM Edit>
PCM Edit> sh scan SCAN$BRSADV
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
Scan Name       = SCAN$BRSADV
    Information = Scan profile for system BRSADV.
    Events (0)
    Scans (11)
      DCPS           Events of DECprint supervisor
      DECPS          Events of DECPS listener
      OpenVMS_VAX_V6 Events of OpenVMS VAX V6.* 
      SCHEDULER      Events of Scheduler
      SECURITY       Events of AUDIT_SERVER listener
      SHADOWING      Events of host based shadowing.
      SLS            Events of Storage Library system
      UCX            Events of VMS Services for TCP/IP
      VAX7000        Events of VAX 7000 HW series.
      VAXclusterV6   Events of OpenVMS for VAX V6.*
PCM Edit>
PCM Edit>
PCM Edit> sh scan SCAN$DOMUS
Full or Brief listing? [f=full, b=brief] (b): f
Output file (SYS$OUTPUT):
Scan Name       = SCAN$DOMUS
    Information = Scan profile for system BRSADV.
    Events (0)
    Scans (6)
      DCPS           Events of DECprint supervisor
      DECPS          Events of DECPS listener
      OpenVMS_VAX_V5 Events of OpenVMS VAX V5.* 
      SECURITY       Events of AUDIT_SERVER listener
      SLS            Events of Storage Library system
      VAX4200        Events of VAX 4200 HW series.
PCM Edit>





Bear in mind that just having "a" scan profile makes no sense, a scan profile
should be reviewed after every new release of a layered product, a operating
system ect. It is the "quality" of the scan profile that determines the benefits
You have from it when used in VCS/PCM/PEM .

Don't underestimate the work that has to be put in this area!
It is worth the investment, as the product VCS or PCM or PEM stands or falls
with the quality (besides the bugs leftover in PCM) of these scan profiles! 
They should be released "more" often as VCS or PCM was released, as the
collection of layered products, HW ect, changes more "often" than the realease
timeframes of VCS/PCM .


What I needed within the 5 years I used VCS/PCM is mainly OpenVMS oriented:

Hardware specific messages:
Any VAX or AXP (lets say any processor meaaages from introduction date of
the MV3100 off) messages of importance
HSC,HSJ,HSZ messages
IBM RS6000 messages
HP 9000 messages

Operating system messages
OPENVMS_AXP_V6  OpenVMS for AXP V6 operating system messages
OPENVMS_VAX_V6  OpenVMS for VAX V5 operating system messages (yes they are different)
OPENVMS_VAX_V5  OpenVMS for VAX V5 operating system messages (yes they are different)
VAXCLUSTERV5	OpenVMS VAXcluster V5 messages (yes they are different) 
VAXCLUSTERV6    OpenVMS VAXcluster V6 messages (yes they are different) 
VMSCLUSTERV6    OpenVMS AXPcluster V6 messages (yes they are different) 
OSF1            OSF/1 operating system messages
IBM-AIX		AIX messages
HP-UX messages  HP-UX messages

Layered product messages
SCHEDULER	DECscheduler
SHADOWING	OpenVMS shadowing
SLS		Storage library system
PAB     	Polycenter archive backup
HSM		Hirarchical storage manager
DFO     	File optimiser messages
UCX     	TCP/IP services for OpenVMS
ACB             Automatic callback messages (PASS, not a layered product)
DCPS            Print supervisor messages
DECPS		Performance solution messages
NSR             Network save and restore
RDB		RDB messages
ORACLE		ORACLE messages

Erik.

Re .-2

Tony,

I don't understand your issue here. Scan profiles can contain other scan
profiles, so you can build up a VMS scan profile that will also contain the
layered products you want/need. You shouldn't have node specific ones - although
(if my memory serves me correctly) that is what Steve McGinley decided to do - I
disagreed with him. The whole concept of VCS/PCM was around generic scan
profiles. Unfortunately, due to the politics involved with the site you work on,
I can't help you.

re.-1

Erik,

I'm glad I've been able to craete so many scan profiles for you that you need
(SLS, Scheduler, Networker) ;-)

Shaun

    Erik
    
    I can agree with version specific scans, if I wanted a product scan I
    could create one with the appropriate specific ones as subscans. It
    would be really nice if events whose search-for-string was the same
    version to version had the same name, and events whose
    search-for-string was different version to version had different names.
    
    
    Mr Elliss
    
    One of the beauties of a lot of Digital software is that it offers
    generic solutions to specific problems. PCM is no exception. If a site
    has a number of managed systems that have very similar software
    profiles I would not hesitate to advise them to set up a generic scan
    and define each managed system's scan as this. If a site has a number
    of managed systems that have disparate software profiles I might advise
    them to set up a scan per node. As I pointed out in my reply, it is a
    juggling act between the amount of management needed, and the amount of
    computer resources available.
    
    Horses for courses - and I fear that tomorrow it may be a Pommy stayer,
    used to running in heavy conditions that takes our Melbourne Cup from us
    - again.
    
    
    Method of Distribution?
    
    One thing that has not been addressed in this note so far is the method
    of updating these scans. Breaking the ice I would suggest that each set
    of software CDs has the latest scans on them, and that these should be
    installed into the CONSOLE$SCANS directory. It would then be up to the
    PCM person to update the configuration as necessary...
    
    
    Tony Sherrard

    To add to what Tony said about distribution I would like to see these
    made available electronically via a WWW page as well as the DSNlink and
    DIA systems.
    
    Regs,
      Dan

    Hi!
    
    I'd like to see scans for AppleTalk!
    We have had some serious problems with ATK that were not detected because
    there were no ATK scans (they don't have PCM yet - but...), the system
    disks were filling up rapidly because OPCOM was screaming.
    
    It can't be many events but they are bursting out in a rapid pace so...
    
    
    /Staffan

    
    
    Hi,
    
    A customer of mine is after scan profiles for the following systems
    
    dec 2100 and dec 2000/300
    
    Any help greatly appreciated
    
    Avril Nicholson
    Digital OpenVMS Group
    7833 3105

Avril,

I started on the 2100/2000 series. If you look in the note for scan profiles
you'll find it.

It includes UNIX.

There is, though, only a couple of events. Something is better than nothing

Shaun

    
    Thanks for the reply, I have looked at the locations pointed to by the
    notes conference and I can't seem to find it. Could you confirm the
    location please.
    
    Kind regards
    Avril Nicholson 

    Thank you all for your lists of needed scan profiles as well as the
    comments and suggestions as to HOW to actually provide them.  I'm using
    this reply as a marker of what's been added to the list we'll be
    using to build from.  Please continue to keep the requests coming
    and reply to this note.  Please also reply to note 614 if you have
    a profile to add to our existing collection.

    
    See note 614.17 for a DECnet/OSI scan profile I've written.
    
    Tony Parsons,
    Sydney CSC.