[prev in list] [next in list] [prev in thread] [next in thread]
List: opennms-buglist
Subject: [Buglist] [JIRA] (NMS-3913) linkd not showing links between nodes and cisco switches
From: jira () opennms ! org (Aaron Scamehorn (JIRA))
Date: 2011-12-16 19:02:43
Message-ID: 1087807319.98.1324062163326.JavaMail.jira () mail1 ! opennms ! com
[Download RAW message or body]
[ http://issues.opennms.org/browse/NMS-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]
Aaron Scamehorn reopened NMS-3913:
----------------------------------
Re-openning this issue. See previous comment.
> linkd not showing links between nodes and cisco switches
> --------------------------------------------------------
>
> Key: NMS-3913
> URL: http://issues.opennms.org/browse/NMS-3913
> Project: OpenNMS
> Issue Type: Bug
> Components: Maps/Linkd
> Affects Versions: 1.8.0
> Environment: Operating System: Linux
> Platform: PC
> Reporter: William
> Assignee: Seth Leger
> Fix For: 1.9.94
>
> Attachments: cc-4900m-1-141_walk.out, cc-c2651xm-1_walk.out, cc-c2811-eq_walk.out, \
> cc-c2821-ny-1_walk.out, cc-c3550-dmz_walk.out, cc-c3560-eq-1_walk.out, \
> cc-c3750stack_walk.out, cc-dl1228-dmz_walk.out, cc-mgmt1-ny_walk.out, link.log, \
> sentry_walk.out, src-linkd.patch
>
> I enabled the linkd daemon within opennms and the simple test was adding opennms \
> box and the cisco switch with snmp and wait unitil the links show up in the node \
> link detail but that does not happen. When i manually snmpwalk the switch i can \
> grep on mac and ip adres and they are both there but no links within opennms. i'm a \
> bit lost because it should just work as i have read on the wiki page. My cisco is \
> an 1.324 and has ip adres 192.168.0.11 and my nms box has 192.168.0.233. With kind \
> regards William van de Velde
> My linkd config:
> #########################
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <linkd-configuration threads="5" initial_sleep_time="360000"
> snmp_poll_interval="1800000" discovery_link_interval="30000">
>
>
> <!--
>
> Here is a list of sys oids and corresponding classes to get
> SNMP vlan info from nodes.
> Verify that your switch devices sys oids are in the following lists
> if you want to get informations on Vlans!
> Otherwise:
> Put your own sys oids in the proper vendor tag and specify sys oid
> using <specific> and <include-range> tags
>
> -->
>
> <vlans>
> <vendor vendor_name="3Com" sysoidRootMask=".1.3.6.1.4.1.43"
> class-name="org.opennms.netmgt.linkd.snmp.ThreeComVlanTable">
> <specific>1.9.13.3.1</specific>
> <specific>10.27.4.1.2.2</specific>
> <specific>10.27.4.1.2.4</specific>
> <specific>10.27.4.1.2.11</specific>
> <specific>1.16.4.3.5</specific>
> <specific>1.16.4.3.6</specific>
> </vendor>
> <vendor vendor_name="3Com3870" sysoidRootMask=".1.3.6.1.4.1.43.1"
> class-name="org.opennms.netmgt.linkd.snmp.Dot1qStaticVlanTable">
> <specific>8.43</specific>
> <specific>8.61</specific>
> </vendor>
> <vendor vendor_name="Nortel" sysoidRootMask=".1.3.6.1.4.1.45.3"
> class-name="org.opennms.netmgt.linkd.snmp.RapidCityVlanTable">
> <specific>61.1</specific>
> <specific>35.1</specific>
> <specific>53.1</specific>
> </vendor>
> <vendor vendor_name="Intel" sysoidRootMask=".1.3.6.1.4.1.343.5"
> class-name="org.opennms.netmgt.linkd.snmp.IntelVlanTable">
> <specific>1.5</specific>
> </vendor>
> <vendor vendor_name="HP Networks" sysoidRootMask=".1.3.6.1.4.1.11.2.3.7"
> class-name="org.opennms.netmgt.linkd.snmp.Dot1qStaticVlanTable">
> <specific>11.1</specific>
> <specific>11.3</specific>
> <specific>11.13</specific>
> <specific>11.14</specific>
> <specific>11.18</specific>
> <specific>11.19</specific>
> <specific>11.20</specific>
> <specific>11.23</specific>
> <specific>11.27</specific>
> <specific>11.29</specific>
> <specific>11.32</specific>
> <specific>11.45</specific>
> <specific>11.50</specific>
> <specific>11.63</specific>
> <specific>11.66</specific>
> <specific>11.81</specific>
> <include-range begin="11.6" end="11.11"/>
> </vendor>
> <vendor vendor_name="cisco" sysoidRootMask=".1.3.6.1.4.1.9"
> class-name="org.opennms.netmgt.linkd.snmp.CiscoVlanTable">
> <specific>1.217</specific>
> <specific>1.218</specific>
> <specific>1.222</specific>
> <specific>1.221</specific>
> <specific>1.246</specific>
> <specific>1.247</specific>
> <specific>1.248</specific>
> <specific>1.278</specific>
> <specific>1.282</specific>
> <specific>1.283</specific>
> <specific>1.300</specific>
> <specific>1.370</specific>
> <specific>1.324</specific>
> <specific>1.325</specific>
> <specific>1.366</specific>
> <specific>1.367</specific>
> <specific>1.400</specific>
> <specific>1.427</specific>
> <specific>1.428</specific>
> <specific>1.429</specific>
> <specific>1.431</specific>
> <specific>1.448</specific>
> <specific>1.502</specific>
> <specific>1.503</specific>
> <specific>1.516</specific>
> <specific>1.542</specific>
> <specific>1.559</specific>
> <specific>1.561</specific>
> <specific>1.563</specific>
> <specific>1.564</specific>
> <specific>1.565</specific>
> <specific>1.578</specific>
> <specific>1.616</specific>
> <specific>1.617</specific>
> <specific>1.618</specific>
> <specific>1.626</specific>
> <specific>1.633</specific>
> <specific>1.634</specific>
> <specific>1.694</specific>
> <specific>1.696</specific>
> <specific>1.697</specific>
> <specific>1.716</specific>
> <specific>1.745</specific>
> <specific>1.748</specific>
> <specific>1.798</specific>
> <specific>5.7</specific>
> <specific>5.17</specific>
> <specific>5.18</specific>
> <specific>5.20</specific>
> <specific>5.28</specific>
> <specific>5.34</specific>
> <specific>5.36</specific>
> <specific>5.41</specific>
> <specific>5.42</specific>
> <specific>5.46</specific>
> <specific>5.49</specific>
> <specific>5.51</specific>
> <specific>5.59</specific>
> </vendor>
> <vendor vendor_name="Extreme Networks" sysoidRootMask=".1.3.6.1.4.1.1916"
> class-name="org.opennms.netmgt.linkd.snmp.ExtremeNetworkVlanTable">
> <specific>2.11</specific>
> <specific>2.14</specific>
> <specific>2.28</specific>
> <specific>2.63</specific>
> </vendor>
> </vlans>
> <!--
> It's possible in packages to overwrite all properties - (thread and \
> initial_sleep_time) in the linkd-configuration
> -->
>
> <package name="LAN" use-bridge-discovery="false" use-ip-route-discovery="false" \
> enable-vlan-discovery="true" use-cdp-discovery="true" \
> save-stp-interface-table="true" save-stp-node-table="true" save-route-table="true" \
> > <filter>IPADDR != '0.0.0.0'</filter>
> <include-range begin="192.168.0.1" end="192.168.0.254"/>
> </package>
> <package name="LAN2" use-bridge-discovery="false" use-ip-route-discovery="true" \
> save-route-table="true" > <filter>IPADDR != '0.0.0.0'</filter>
> <include-range begin="192.168.0.1" end="192.168.0.254"/>
> </package>
> <package name="LINUX-ETHERNET-ROUTERS-LAN" \
> force-ip-route-discovery-on-ethernet="true"> <filter>IPADDR != '0.0.0.0'</filter>
> <include-range begin="192.168.0.1" end="192.168.0.254"/>
> </package>
>
> <!-- Use more packages with huge network-->
> <!-- here is a configuration that is valid on ethernet LANs -->
> <!--
> <package name="LAN" use-ip-route-discovery="false">
> <filter>IPADDR != '0.0.0.0'</filter>
> <include-range begin="10.1.1.1" end="10.1.1.254"/>
> </package>
> -->
> <!-- here is a configuration valid on WAN where linkd try to get
> links using cisco discovery protolol first and then routers ip route tables \
> --> <!--
> <package name="WAN" use-bridge-discovery="false">
> <filter>IPADDR != '0.0.0.0'</filter>
> <include-range begin="10.1.1.1" end="10.1.1.254"/>
> </package>
> -->
> <!-- here is a configuration in which you have to find links when using cross \
> ethernet cables among router. Linkd by default finds links on LAN using bridge \
> forwarding table becouse it guess that the node is linked to a switch port. By \
> the way there are situations in which you can have some routers connected via \
> cross ethernet cables. So this is a way to find that links.
> -->
> <!--
> <package name="LINUX-ETHERNET-ROUTERS" force-ip-route-discovery-on-ethernet="true">
> <filter>IPADDR != '0.0.0.0'</filter>
> <include-range begin="10.1.1.1" end="10.1.1.254"/>
> </package>
> -->
> <!-- do you want that linkd send a new suspect event for each ip address found on \
> devices? --> <!--
> <package name="AUTODISCOVERY" auto-discovery="true">
> <filter>IPADDR != '0.0.0.0'</filter>
> <include-range begin="10.1.1.1" end="10.1.1.254"/>
> </package>
>
> -->
> </linkd-configuration>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
http://issues.opennms.org/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic