Node Label & Provisioning

Hello *,

I am working on an OpenNMS implementation for an enterprise network. This
network consists of a few hundred network nodes. I am running OpenNMS
version 1.8.5 on Ubuntu 10.04 LTS.

I am struggling with a few problems, which are not clear to me. I can not
find any information on it, which makes things clear for me.

== Node Labels ==

The first question is regarding the node labels. For provisioning and
integration with Rancid, the right node labels are important to me. On the
OpenNMS website (
http://www.opennms.org/wiki/FAQ-Troubleshooting#Q:_How_are_node_labels_determined.3F),
I found the list of rules on how node labels are defined.

There is stated that the lowest numbered interface is used to do a reverse
lookup. Now I did some research on how this actually works and get the
following outcommings. I have two core switches, which have something like
30 interfaces (vlan, loopback, physical, hsrp).

The interface that is used on one of the switches is the lowest VLAN
interface. On the other switches it is the lowest HSRP interface. The
problem with this, is that it is hard to use that kind of interfaces on a
switch to give the right reverse dns information. What I want is the lowest
loopback interface (like more network protocols use). This would make the
implementation of OpenNMS and the correct (automatic) node label so much
easier, but I cannot find out how to do this. Regarding the few hundreds of
nodes, manual configuration of the node labels is not an efficient option.

== Provisioning ==

http://opennms.org/w/images/c/ca/ProvisioningUsersGuide.pdf
I want to use provisioning to let OpenNMS automatically assign the nodes to
the group with corresponding scans. I tried this using the web interface
Admin -> Provisioning Groups.

I created some policies to test how provisioning works. What I expect is
that a node matching a policy is added automatically to the provisioning
group, but this doesn´t happen. I deleted the nodes from OpenNMS and let
them be rediscovered with no success.

I started with the syntax from the user guide mentioned above for IP
addresses. Later I tried it with single IP addresses to be sure I am not
using a invalid key to match on. I also tested my regex with grep -E
¨<regex>¨ to verify if they are working.

In the opennms.properties, I configured:
org.opennms.provisiond.enableDiscovery=true

The rest of the configuration is done via the webinterface like I mentioned
above. I think I am really missing something, because nothing happens with
the provisioning, but I cannot find out what...

This feature looks to me like a very nice feature, but until now, I did not
get it working. Somewhere else on the mailing list, someone talks about
disabling capsd. I cannot find out how to do this? Could this be the
problem?

If someone could help me solving some problems or make things more clear for
me, or could point me in the right direction, would really help me! Thanks
in advance!


Kind regards,

Marvin

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-install mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-install