[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-install
Subject:    Re: [opennms-install] Problem with Link layer discovery
From:       Pedro Jimenez <pedrojg84 () hotmail ! com>
Date:       2012-03-02 11:03:42
Message-ID: BLU125-W2172FE4C936FE9198BDAFFA26D0 () phx ! gbl
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Thank you Michael, I'll try on opennms-discuss then.

From: Michael.Seibold@barmer-gek.de
To: opennms-install@lists.sourceforge.net
Date: Mon, 27 Feb 2012 16:25:51 +0000
Subject: Re: [opennms-install] Problem with Link layer discovery











Hi Pedro,
 
this is the opennms-install mailing list, you should write this to opennms-discuss \
instead.  
Did you add check if the sysoid of your devices are included in the \
linkd-configuration.xml? See

http://www.opennms.org/wiki/Linkd#Daemon_Configuration
 
- Michael





Von: Pedro Jimenez Garcia [mailto:pedrojg84@hotmail.com]


Gesendet: Freitag, 24. Februar 2012 10:37

An: opennms-install@lists.sourceforge.net

Betreff: [opennms-install] Problem with Link layer discovery





Hi all!



I'm working with OpenNMS to manage a network, but I haven´t been able to discover L2 \
links. Devices are Allied telesis x900 switches, I'm working with the WMware version \
of OpenNMS, Linkd is up... and when I check "View Node Link Detailed Info" I get the \
whole  table, but "Links" column is empty.



Googling I have found a post wrote 3 years ago on "OpenNMS discuss" about "Linkd and \
LLDP" talking about some OID's to consider:

[Snmpwalks of my device included]

- 1.0.8802.1.1.2.1.3.3 

iso.0.8802.1.1.2.1.3.3.0 = STRING: "Labo20"   --->> Ok, that's the hostname of the \
device I want to monitor.



- 1.0.8802.1.1.2.1.3.7.1.3

iso.0.8802.1.1.2.1.3.7.1.3.1 = STRING: "port1.0.1"    --->> Ok, 12 ports on Labo20 \
named port1.0.1 to 12.

iso.0.8802.1.1.2.1.3.7.1.3.2 = STRING: "port1.0.2"

iso.0.8802.1.1.2.1.3.7.1.3.3 = STRING: "port1.0.3"

iso.0.8802.1.1.2.1.3.7.1.3.4 = STRING: "port1.0.4"

iso.0.8802.1.1.2.1.3.7.1.3.5 = STRING: "port1.0.5"

iso.0.8802.1.1.2.1.3.7.1.3.6 = STRING: "port1.0.6"

iso.0.8802.1.1.2.1.3.7.1.3.7 = STRING: "port1.0.7"

iso.0.8802.1.1.2.1.3.7.1.3.8 = STRING: "port1.0.8"

iso.0.8802.1.1.2.1.3.7.1.3.9 = STRING: "port1.0.9"

iso.0.8802.1.1.2.1.3.7.1.3.10 = STRING: "port1.0.10"

iso.0.8802.1.1.2.1.3.7.1.3.11 = STRING: "port1.0.11"

iso.0.8802.1.1.2.1.3.7.1.3.12 = STRING: "port1.0.12"



- 1.0.8802.1.1.2.1.4.1.1.7

iso.0.8802.1.1.2.1.4.1.1.7.4551.12.2 = STRING: "port1.0.24"    --->> Ok, \
"destination" ports.

iso.0.8802.1.1.2.1.4.1.1.7.59868725.11.5 = STRING: "port1.0.23"



- 1.0.8802.1.1.2.1.4.1

iso.0.8802.1.1.2.1.4.1.1.4.4551.12.2 = INTEGER: 4

iso.0.8802.1.1.2.1.4.1.1.4.59868725.11.5 = INTEGER: 4

iso.0.8802.1.1.2.1.4.1.1.5.4551.12.2 = Hex-STRING: 00 00 CD 29 A9 97 

iso.0.8802.1.1.2.1.4.1.1.5.59868725.11.5 = Hex-STRING: 00 00 CD 29 A9 97 

iso.0.8802.1.1.2.1.4.1.1.6.4551.12.2 = INTEGER: 1

iso.0.8802.1.1.2.1.4.1.1.6.59868725.11.5 = INTEGER: 1

iso.0.8802.1.1.2.1.4.1.1.7.4551.12.2 = STRING: "port1.0.24"

iso.0.8802.1.1.2.1.4.1.1.7.59868725.11.5 = STRING: "port1.0.23"

iso.0.8802.1.1.2.1.4.1.1.8.4551.12.2 = STRING: "ChannelTo192.168.2.20"

iso.0.8802.1.1.2.1.4.1.1.8.59868725.11.5 = STRING: "ChannelTo192.168.2.20"

iso.0.8802.1.1.2.1.4.1.1.9.4551.12.2 = STRING: "Labo30"

iso.0.8802.1.1.2.1.4.1.1.9.59868725.11.5 = STRING: "Labo30"

iso.0.8802.1.1.2.1.4.1.1.10.4551.12.2 = STRING: "Allied Telesis router/switch, AW+ \
v5.4.1-1.3"

iso.0.8802.1.1.2.1.4.1.1.10.59868725.11.5 = STRING: "Allied Telesis router/switch, \
AW+ v5.4.1-1.3"

iso.0.8802.1.1.2.1.4.1.1.11.4551.12.2 = STRING: "("

iso.0.8802.1.1.2.1.4.1.1.11.59868725.11.5 = STRING: "("

iso.0.8802.1.1.2.1.4.1.1.12.4551.12.2 = STRING: "("

iso.0.8802.1.1.2.1.4.1.1.12.59868725.11.5 = STRING: "("

--->> and this last one, specifying ports 11 and 12 are connected to 23 and 24 on \
Labo30, and their MAC, description, etc...



As I said, Linkd is up and I have added [to link-configuration.xml] to enable polling \
for this device:



<package name="PruebaDiscovery" auto-discovery="true" use-cdp-discovery="true" \
use-ip-route-discovery="true"

enable-vlan-discovery="true" use-bridge-discovery="true" save-route-table="true" \
save-stp-node-table="true" save-stp-interface-table="true">

<filter>IPADDR!='0.0.0.0'</filter>

<include-range begin="192.168.2.1" end="192.168.2.101"/>

</package>



These are the last lines on link.log:

2012-02-24 10:08:55,052 WARN  [OpenNMS.Linkd] Linkd: wakeUpNodeCollection: schedulink \
a node not found: 7

2012-02-24 10:08:55,143 WARN  [OpenNMS.Linkd] Linkd: scheduleNodeCollection: Failed \
to get Linkable node from DataBase. Exiting





¿Could anybody give me a hint about what to change/check? 



Thanks in advance!





------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
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 		 	   		  


[Attachment #5 (text/html)]

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Thank you Michael, I'll try on opennms-discuss then.<br><br><div><div \
id="SkyDrivePlaceholder"></div><hr id="stopSpelling">From: \
Michael.Seibold@barmer-gek.de<br>To: opennms-install@lists.sourceforge.net<br>Date: \
Mon, 27 Feb 2012 16:25:51 +0000<br>Subject: Re: [opennms-install] Problem with Link \
layer discovery<br><br>


<meta http-equiv="Content-Type" content="text/html; charset=unicode">
<meta name="Generator" content="Microsoft SafeHTML">

<style>
.ExternalClass .ecxhmmessage P
{padding-bottom:0px;padding-left:0px;padding-right:0px;padding-top:0px;}
.ExternalClass BODY.ecxhmmessage
{font-family:Tahoma;font-size:10pt;}
</style>



<div dir="ltr" align="left"><span class="ecx972182016-27022012"><font color="#0000ff" \
face="Arial">Hi Pedro,</font></span></div> <div dir="ltr" align="left"><span \
class="ecx972182016-27022012"><font color="#0000ff" \
face="Arial"></font></span>&nbsp;</div> <div dir="ltr" align="left"><span \
class="ecx972182016-27022012"><font color="#0000ff" face="Arial">this is the \
opennms-install mailing list, you should write this to opennms-discuss \
instead.</font></span></div> <div dir="ltr" align="left"><span \
class="ecx972182016-27022012"><font color="#0000ff" \
face="Arial"></font></span>&nbsp;</div> <div dir="ltr" align="left"><span \
class="ecx972182016-27022012"><font color="#0000ff" face="Arial">Did you add check if \
the sysoid of your devices are included in the linkd-configuration.xml? See \
</font></span></div> <div dir="ltr" align="left"><span \
class="ecx972182016-27022012"><font color="#0000ff" face="Arial"><a \
href="http://www.opennms.org/wiki/Linkd#Daemon_Configuration" \
target="_blank">http://www.opennms.org/wiki/Linkd#Daemon_Configuration</a></font></span></div>
 <div dir="ltr" align="left"><span class="ecx972182016-27022012"><font \
color="#0000ff" face="Arial"></font></span>&nbsp;</div> <div align="left"><font \
face="Arial"><span class="ecx972182016-27022012">- </span>Michael </font></div>
<br>
<div dir="ltr" class="ecxOutlookMessageHeader" lang="de" align="left">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>Von:</b> Pedro Jimenez Garcia \
[mailto:pedrojg84@hotmail.com] <br>
<b>Gesendet:</b> Freitag, 24. Februar 2012 10:37<br>
<b>An:</b> opennms-install@lists.sourceforge.net<br>
<b>Betreff:</b> [opennms-install] Problem with Link layer discovery<br>
</font><br>
</div>
<div></div>
<div dir="ltr">Hi all!<br>
<br>
I'm working with OpenNMS to manage a network, but I haven´t been able to discover L2 \
links. Devices are Allied telesis x900 switches, I'm working with the WMware version \
of OpenNMS, Linkd is up... and when I check "View Node Link Detailed Info" I get the \
whole  table, but "Links" column is empty.<br>
<br>
Googling I have found a post wrote 3 years ago on "OpenNMS discuss" about "Linkd and \
LLDP" talking about some OID's to consider:<br> [Snmpwalks of my device included]<br>
- <b>1.0.8802.1.1.2.1.3.3 </b><br>
iso.0.8802.1.1.2.1.3.3.0 = STRING: "Labo20"&nbsp;&nbsp; ---&gt;&gt; Ok, that's the \
hostname of the device I want to monitor.<br> <br>
- <b>1.0.8802.1.1.2.1.3.7.1.3</b><br>
iso.0.8802.1.1.2.1.3.7.1.3.1 = STRING: "port1.0.1"&nbsp;&nbsp;&nbsp; ---&gt;&gt; Ok, \
12 ports on Labo20 named port1.0.1 to 12.<br> iso.0.8802.1.1.2.1.3.7.1.3.2 = STRING: \
"port1.0.2"<br> iso.0.8802.1.1.2.1.3.7.1.3.3 = STRING: "port1.0.3"<br>
iso.0.8802.1.1.2.1.3.7.1.3.4 = STRING: "port1.0.4"<br>
iso.0.8802.1.1.2.1.3.7.1.3.5 = STRING: "port1.0.5"<br>
iso.0.8802.1.1.2.1.3.7.1.3.6 = STRING: "port1.0.6"<br>
iso.0.8802.1.1.2.1.3.7.1.3.7 = STRING: "port1.0.7"<br>
iso.0.8802.1.1.2.1.3.7.1.3.8 = STRING: "port1.0.8"<br>
iso.0.8802.1.1.2.1.3.7.1.3.9 = STRING: "port1.0.9"<br>
iso.0.8802.1.1.2.1.3.7.1.3.10 = STRING: "port1.0.10"<br>
iso.0.8802.1.1.2.1.3.7.1.3.11 = STRING: "port1.0.11"<br>
iso.0.8802.1.1.2.1.3.7.1.3.12 = STRING: "port1.0.12"<br>
<br>
- <b>1.0.8802.1.1.2.1.4.1.1.7</b><br>
iso.0.8802.1.1.2.1.4.1.1.7.4551.12.2 = STRING: "port1.0.24"&nbsp;&nbsp;&nbsp; \
---&gt;&gt; Ok, "destination" ports.<br> iso.0.8802.1.1.2.1.4.1.1.7.59868725.11.5 = \
STRING: "port1.0.23"<br> <br>
- <b>1.0.8802.1.1.2.1.4.1</b><br>
iso.0.8802.1.1.2.1.4.1.1.4.4551.12.2 = INTEGER: 4<br>
iso.0.8802.1.1.2.1.4.1.1.4.59868725.11.5 = INTEGER: 4<br>
iso.0.8802.1.1.2.1.4.1.1.5.4551.12.2 = Hex-STRING: 00 00 CD 29 A9 97 <br>
iso.0.8802.1.1.2.1.4.1.1.5.59868725.11.5 = Hex-STRING: 00 00 CD 29 A9 97 <br>
iso.0.8802.1.1.2.1.4.1.1.6.4551.12.2 = INTEGER: 1<br>
iso.0.8802.1.1.2.1.4.1.1.6.59868725.11.5 = INTEGER: 1<br>
iso.0.8802.1.1.2.1.4.1.1.7.4551.12.2 = STRING: "port1.0.24"<br>
iso.0.8802.1.1.2.1.4.1.1.7.59868725.11.5 = STRING: "port1.0.23"<br>
iso.0.8802.1.1.2.1.4.1.1.8.4551.12.2 = STRING: "ChannelTo192.168.2.20"<br>
iso.0.8802.1.1.2.1.4.1.1.8.59868725.11.5 = STRING: "ChannelTo192.168.2.20"<br>
iso.0.8802.1.1.2.1.4.1.1.9.4551.12.2 = STRING: "Labo30"<br>
iso.0.8802.1.1.2.1.4.1.1.9.59868725.11.5 = STRING: "Labo30"<br>
iso.0.8802.1.1.2.1.4.1.1.10.4551.12.2 = STRING: "Allied Telesis router/switch, AW+ \
v5.4.1-1.3"<br> iso.0.8802.1.1.2.1.4.1.1.10.59868725.11.5 = STRING: "Allied Telesis \
router/switch, AW+ v5.4.1-1.3"<br> iso.0.8802.1.1.2.1.4.1.1.11.4551.12.2 = STRING: \
"("<br> iso.0.8802.1.1.2.1.4.1.1.11.59868725.11.5 = STRING: "("<br>
iso.0.8802.1.1.2.1.4.1.1.12.4551.12.2 = STRING: "("<br>
iso.0.8802.1.1.2.1.4.1.1.12.59868725.11.5 = STRING: "("<br>
---&gt;&gt; and this last one, specifying ports 11 and 12 are connected to 23 and 24 \
on Labo30, and their MAC, description, etc...<br> <br>
As I said, Linkd is up and I have added [to link-configuration.xml] to enable polling \
for this device:<br> <br>
&lt;package name="PruebaDiscovery" auto-discovery="true" use-cdp-discovery="true" \
use-ip-route-discovery="true"<br> enable-vlan-discovery="true" \
use-bridge-discovery="true" save-route-table="true" save-stp-node-table="true" \
save-stp-interface-table="true"&gt;<br> \
&lt;filter&gt;IPADDR!='0.0.0.0'&lt;/filter&gt;<br> &lt;include-range \
begin="192.168.2.1" end="192.168.2.101"/&gt;<br> &lt;/package&gt;<br>
<br>
These are the last lines on link.log:<br>
2012-02-24 10:08:55,052 WARN&nbsp; [OpenNMS.Linkd] Linkd: wakeUpNodeCollection: \
schedulink a node not found: 7<br> 2012-02-24 10:08:55,143 WARN&nbsp; [OpenNMS.Linkd] \
Linkd: scheduleNodeCollection: Failed to get Linkable node from DataBase. Exiting<br> \
<br> <br>
¿Could anybody give me a hint about what to change/check? <br>
<br>
Thanks in advance!<br>
</div>


<br>------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2<br>_______________________________________________
 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</div> 		 	   		  \
</div></body> </html>



------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

_______________________________________________
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

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic