Re: Collect data from physical switchports
David Albrecht <[email protected]>
| Newsgroups | gmane.network.opennms.general |
|---|---|
| Message-ID | <CAD-EOiD5HPNHZ-qT+3vmt5ZT2kiwL_QmHCjtX7XWtdRAdtkJJA@mail.gmail.com> |
Norbert, As the others have said, you need to use a Provisioning Requisition to do this. I just did nearly the same thing, but on a couple hundred Cisco switches that have the "TenGigabitEthernet" and "GigabitEthernet" ports, so here's some pointers that I have for you. In the edit mode of a provisioning requisition, click on Edit Definition, then Policies, then add policy. Name it something that is meaningful to you - I have mine called "EnableCollection". Then you'll need to fill in the following fields. Here's a picture of how I have mine. [image: Inline image 1] Note the value in the ifName field. This is a regular expression that will enable collection on any interface beginning with "Te" (for TenGigabitEthernet ports), "Gi" (for GigabitEthernet ports), "Po" (for any Port-channel interface), and Vl77 (Vlan77, my management interface). I couldn't get the automatic discovery to work properly and every time I ran the scan with different IP subranges meant for different provisioning requisitions, none of the switches would show up in the requisition. I manually edited the xml files for each requisition in the $OPENNMS_HOME/etc/imports folder, then refreshed the entire requisition. I created an Excel document to generate the xml string for each device in my environment so modifying the etc/imports/*.xml files was as easy as copying and pasting. While we're on the same subject, if anyone else here has any idea why the automated discovery would not add my switches to the requisition, I'd love to hear them! I am new to OpenNMS and found that it was very difficult to get setup the way I needed. Hope this helps you, Norbert. On Fri, Jan 12, 2018 at 3:55 AM, Norbert Steinhoff < [email protected]> wrote: > Thumbs up. > > That’s it. > > > Thanks > Norbert > > Am 12.01.2018 um 12:37 schrieb Ronny Trommer <[email protected]>: > > Hi Norbert, > > a way to do this is using a MatchingSnmpInterfacePolicy for the > requisition your switches are in. The basic idea is for each physical > interface is evaluated against some attributes. In the example attached > I’ve enabled data collection for all interfaces with operstatus UP (1). > > You can do also enable those for interface types or a combination of them. > If you want a little bit more control, you can also use a regex against the > ifAlias which can be set on the device. > > Hope this helps. > > > <interface-datacollection.png> > > On 12. Jan 2018, at 12:15, Norbert Steinhoff <[email protected]> > wrote: > > Hi all, > > I'm looking for an easy solution for the following requirement: > > In our branches we use Cisco Routers with 4 Port switchcards (HWIC/NIM-ES4 > etc) > The ports of these cards work as vlan trunk or for specific devices in > access mode. > > By default, opennms does not collect metrics of these interfaces. > I suggest because they have no ip assigned and so i need to activate > datacollection > manually in "Configure SNMP Data Collection per Interface" > > For hundreds of routers... uuuh > > Is there a way in the config of opennms to activate datacollection on all > physical ports depending on a surveillance category (eg. > DataCollect-SWitchports) ? > > Thanks in advance > Norbert > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ > _________________________________________ > 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 > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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 > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > 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 > -- David ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ 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
image.png
(image/png, 39.5 KB) - not displayed