[MyNMS-users] The story so far ...

[John S. <joh...@nt...>]

to summarise email discussions past, here is a summary of issues

The version on sourceforge is actually 1.01 or something like that: I
released a revised version a day or so after the original. I can't remember
atm what that fixed (a thinko of some sort on my part).


Documentation:
==============
in Installation.html under 'WWW sub-directory structure' I should have
mentioned that you've got to create symlinks (could be hard links) from the
various subdirectories for your users' groups (like noc, etc) and from
Query.cgi in your www directory to /usr/local/myNMS/bin/Query

Linux
=====
(and probably any other Unix except Solaris) in My_Utils.pm we need
something like this:
############################################################################
##
sub ping
{
    my  $devIP = shift or return 1 ;
    my  $PING = $CONFIG{PROG}{PING} or die "CONFIG{PROG}{PING} not defined
in config file";
    # (Linux)ping with 1 second timeout to see if host is up:
    print "$CONFIG{PROG}{PING} $devIP\n";
    `$PING $devIP` =~ /(\d) packets received/
        or die "output of ping was not in expected format (nn packets
received)" ;
    return $1;    #    return the number of packets received (i.e. false is
0)
}
############################################################################
##

SNMP community string
=====================

In SNMP_info, in the subroutine "get_device_snmp_system" you may have to
put:

unless ($SNMP->{sess} )     #   have we got an SNMP session handle?
{
   return 0 unless $SNMP->{IPadd} ;    #   must have an IPadd
   $SNMP->{sess} = new SNMP::Session ( DestHost => $SNMP->{IPadd}, Community
=> 'public');

#^^^^^^^^^^^^^^^^^^^^
}
    or whatever other community string to use (but this ought to be at least
a config parameter, and one might need a scheme for using different
community strings with different hosts).


FreeBSD:
========
There's a problem that Proc::ProcessTable doesn't work for FreeBSD because
"You need access to /dev/kmem to get detailed process information....
scripts using Proc::ProcessTable have to be suid scripts with root and/or
kmem rights" but grokking the output of 'ps' should do the trick.

Perl 5.6
========

if (defined %some_hash)
    now produces warnings: doing
if (%some_hash)
    seems to be the preferred way. This affects My_DButils.pm. I think a:
    perl -pi.bak -e 's/defined \%/%/g;' My_DButils.pm
should fix it.

mySQL
=====

In My_DButils may need to add vars
my  $db_user = '' ;
my  $db_passwd = '' ;
    (or these could be config params)

and after:
 my  $DB = shift || die "$0: sub DB_init must have name of database to
use\n";
 my  $data_source = 'dbi:mysql:' . $DB ; #   use mySQL

change:
     $dbh = DBI->connect($data_source) ;
to:
     $dbh = DBI->connect($data_source, $db_user, $db_passwd) ;

sysServices
===========

the devices on our network (at least, the ones I was interested in) had a
failry clean division between sysServices == 2 for switches, 6 for routers.
Apparently Baystack 450s (at least) use the value 3 so all bits of code to
do with dot1d tables especially needs changing. This isn't as simple a
change as those above.

Query
=====

there seems to be an issue with the HOSTS query not working, but we haven't
got to the bottom of this yet.


 = = = = = = = = = = = = = =

I will roll these up into a new release when I get A Round Tuit: In the
meantime I hope making these changes to the original will not be too
arduous.

regards,
--
John Stumbles                                 http://www.stumbles.org/John
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+