RE: [opennms-install] Small details about OpenNMS

[Chris B. <cb...@fo...>]

1) The nodes with outages just reflect the number of nodes that have some
sort of an outage. How many outages that node has are not taken into
account. The "Overall Service Availability" reflects, I believe, the number
of interfaces with some sort of an outage. Say you have a router with just
an Ethernet and a serial interface - one of each. If the serial interface
went down, that would show one outage in the "Overall Service Availability"
and one in the "Nodes with Outages". But if the node is unavailable, i.e.
you turn it off, then you have 2 interfaces with outages but still just one
node with an outage.

2) Somewhere in the archives is a discussion about what the ordering if for
node-naming. The fact that it's changing on it's own doesn't make sense,
unless DNS is unregistering and registering the name constantly. Many of our
machines come up with the NetBIOS name as the label, but then after entering
a DNS record, the periodic rescan will change the label to be the FQDN. If
you want the specifics, the mailing list archive for opennms-discuss should
have the answer.

Chris Beck, CCNA
Network Administrator
Technology Services, City of Fontana

-----Original Message-----
From: David Williams [mailto:dw...@ma...] 
Sent: Monday, September 08, 2003 9:49 PM
To: in...@li...
Cc: pau...@oi...; gt...@pr...
Subject: [opennms-install] Small details about OpenNMS


Hello all,
First of all, thanks to everyone on the install list for their
contributions.  We are presently using OpenNMS and are pretty happy with
it.

However, there are a few small details we have been noticing.

1)Under the nodes with outages label, sometimes the number of hosts
listed doesn't match up with the number given under Overall Service
Availibilty.  Is this just a matter of SNMP data collection not being in
sync with reported outages in terms of not being in real-time?

2)Events such as a hostname being changed.  For examle, a lot times under
the Nodes with Outages category, OpenNMS will take a DNS entry like

examplehostname.subnetname.domain

and just shorten it to the examplehostname referring to it that way.
The fully qualified domain name will still exist under the Interfaces
label if you click on that node and it will match with the IP. That is
okay.

But, we had a couple of instances where the way that OpenNMS changed the
hostname didn't make sense.

For example, there was an entry in DNS that said for the sake of argument


*	foobar.subnetname.domainname

	The name of the building this machine is in is say, buildingname


*	OpenNMS renamed the node to

	buildingnamefoobar.  The building name is not in the subnet name.


*	I'm guessing there is some kind of Windows NetBIOS naming
	convention going on but can't be sure because we dont't control
	those computers we just monitor them.

	Is there more documentation about naming conventions that we can
	be pointed to for OpenNMS?


	Thanks for all of the help,

	David Williams



______________________________________________________________
(in...@op...)
To subscribe, unsubscribe, or change your list options, go to:
http://lists.opennms.org/mailman/listinfo/install