Miru,
Could you help me out here? I have set up SNMP monitoring for non ip
interfaces such as a serial interface for Administration and Operational
Up/Down, which throws up an alert every time either of those statuses
change. However, I have tons of cisco switch (for example 2960 S), for which
it doesn't detect the change in status when an interface is disconnected,
until a rescan on the node is forced. Any suggestions?
--
View this message in context: http://opennms.530661.n2.nabble.com/SNMP-IfType-for-ethernetCsmacd-tp6599034p6600737.html
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.

The standard syslog protocol has no position for the host where the alarm occurred. So forwarding forwarded syslog messages using 199990's syslog will give you the intermediaries IP address only. syslog-ng has some hooks around this but I don't know if OpenNMS supports these hooks.
Several NetCool folks have also used blooper-ng for trap and syslog forwarding, so you might be able to look into these.
Best regards,
Jonathan
On Jul 19, 2011, at 10:01 AM, Christian Otto Stelter wrote:
> Hi!
>
> We're trying enhance our monitoring (xymon currently) and considering to
> exchange it completely with opennms.
>
> As a first approach we're trying to send the events from xymon to our
> opennms test installation (v1.8.12-1) via syslog (standard redhat
> syslogd not syslog-ng).
>
> The events are being received and displayed in the event view of
> opennms. So the basic configuration seems to work. All events are sent
> by one host (the xymon server) for all hosts monitored by xymon. The
> nodes being monitored are not yet in the node database of opennms.
> Therefore I set new-suspect-host="true" in the syslogd-Config.
>
> I've noticed that in the event information the ip of the interface field
> is changed to the ip of the host according to the host for which the
> event was sent by the xymon server, but not the nodename.
>
> Is there a way to replace the "Node" field also in with the hostname (as
> fqdn) parsed by the syslogd? opennms sets the hostname / nodeid of our
> xymon host which sends the events via syslog.
>
> Or is this information always retrieved from the syslog message and not
> changeable?
>
> Thanks in advance!
>
> Best regards,
>
> Christian Stelter
>
>
> ------------------------------------------------------------------------------
> Magic Quadrant for Content-Aware Data Loss Prevention
> Research study explores the data loss prevention market. Includes in-depth
> analysis on the changes within the DLP market, and the criteria used to
> evaluate the strengths and weaknesses of these DLP solutions.
> http://www.accelacomm.com/jaw/sfnl/114/51385063/
> _______________________________________________
> Please read the OpenNMS Mailing List FAQ:
> http://www.opennms.org/index.php/Mailing_List_FAQ
>
> opennms-discuss mailing list
>
> To *unsubscribe* or change your subscription options, see the bottom of this page:
> https://lists.sourceforge.net/lists/listinfo/opennms-discuss

So my SNMP-Interface-Poller-Configuration.xml has the following interfaces
defined. But I have a switch which has the interface "*ethernetCsmacd* and I
can't figure out the *snmpiftype* for it.
<interface name="Ethernet" criteria="snmpiftype = 6" interval="60000"
user-defined="false" status="on"/>
<interface name="Serial" criteria="snmpiftype = 22" interval="60000"
user-defined="false" status="on"/>
<interface name="SerialPPP" criteria="snmpiftype = 23" interval="60000"
user-defined="false" status="on"/>
<interface name="Multilink" criteria="snmpiftype = 108" interval="60000"
user-defined="false" status="on"/>
I'm trying to configure it so that when an interface is disconnected from
the Cisco Gigabit Switch, it throws up an alarm. It doesn't that for the
other defines interfaces (Ethernet, Serial, SerialPPP, Multilink)
I know my linke should look like
<interface name="ethernetCsmacd" criteria="snmpiftype = ??"
interval="60000" user-defined="false" status="on"/>
but I have no idea what the snmpiftype should be?
--
View this message in context: http://opennms.530661.n2.nabble.com/SNMP-IfType-for-ethernetCsmacd-tp6599034p6599034.html
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.

Do you have the devices that you need to add in a list?
Because I would suggestion getting a script that parses your list of
devices into xml and then rename the file to match the file at
"*/etc/imports.xml".
I have my devices in a csv file in the following format:
DeviceName,IPAddress,Environment,Identifier(Foreign-ID),DeviceType
and a python script runs every night and parses the information into an xml
and replaces the file. That would be a good method to do it.
Your problem is that your set up is telling it to get devices from the
provsioning group and when it's synchonized it doesn't see any devices in
the xml file and deletes everything from your database. I know there's a
setting to change but can't remember it. I'm fairly new to OpenNMS too. If
you'd rather scan an IP range then I'd try getting someone who has a better
knowledge to come in and give some advice.
--
View this message in context: http://opennms.530661.n2.nabble.com/Node-service-Discovery-problem-Discovered-then-deleted-tp5469104p6599016.html
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.

Hi!
We're trying enhance our monitoring (xymon currently) and considering to
exchange it completely with opennms.
As a first approach we're trying to send the events from xymon to our
opennms test installation (v1.8.12-1) via syslog (standard redhat
syslogd not syslog-ng).
The events are being received and displayed in the event view of
opennms. So the basic configuration seems to work. All events are sent
by one host (the xymon server) for all hosts monitored by xymon. The
nodes being monitored are not yet in the node database of opennms.
Therefore I set new-suspect-host="true" in the syslogd-Config.
I've noticed that in the event information the ip of the interface field
is changed to the ip of the host according to the host for which the
event was sent by the xymon server, but not the nodename.
Is there a way to replace the "Node" field also in with the hostname (as
fqdn) parsed by the syslogd? opennms sets the hostname / nodeid of our
xymon host which sends the events via syslog.
Or is this information always retrieved from the syslog message and not
changeable?
Thanks in advance!
Best regards,
Christian Stelter

Nevermind guys, I figured it out! What I had to do was go to Eventconf.xml
and find the respective UEI for Administraion Up/Down and Operational
Up/Down and then I went to notifications.xml and copied a notification and
replaced appropriate data such as description and UEI's. Then restart the
OpenNMS Service and go to WebUI -> Admin->Configure Notifications
->Configure Event Notifications and you're new entries in notifications.xml
should appear there. and voila it's all working, however, I did change my
snmp-interface-poller-configuration.xml and added a few lines. I'll be
documenting it soon and it should be up at http://teknologio.org soon.
--
View this message in context: http://opennms.530661.n2.nabble.com/SNMP-ADM-OP-status-update-tp6598514p6598860.html
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.

Dear All,
I am a beginner in this OpenNMS domain, I want to customize OpenNMS according to our local needs.
At the very first task;
(a) I want to use my company's name "ABCDE" rather than the name "OpenNMS" in the OpenNMS GUI.
(b) I want to change the standard OpenNMS theme with some new Parameter values.
How can I do this ?
Kindly provide your valuable suggestions.
Thanks & Regards,
shamdurgs

I'm not sure if I'm right but I would go ahead to the Admin Page and check
the "Manage Provisioning Nodes" after you add a node and make sure that the
number of nodes define match the number of nodes in the database. What kind
of system are you running? Are you just manually adding a node one by one or
bulk importing or scanning a range for discovery?
--
View this message in context: http://opennms.530661.n2.nabble.com/Node-service-Discovery-problem-Discovered-then-deleted-tp5469104p6598553.html
Sent from the OpenNMS - discuss mailing list archive at Nabble.com.