Quantcast
Channel: THWACK: Document List - Network Performance Monitor
Viewing all articles
Browse latest Browse all 1956

Adding a Rajant device to Solarwinds NPM

$
0
0

SCOPE

This document is applicable to all Rajant devices that need to be added to the Solarwinds NPM

VISION

To have a uniformed procedure of adding a Rajant device to Solarwinds NPM

Requirements

The following may be required when adding a Rajant device to Solarwinds NPM

 

Hardware

Server where existing Solarwinds NPM is deployed

 

Software

Universal Device Poller, which is installed with Solarwinds NPM

SNMPWALK utility which is installed with Solarwinds NPM

 

OVERVIEW

As of this writing, the version of Solarwinds in use is V10.5, and the Solarwinds MIB database file was updated on the 13 June 2014.

The Solarwinds MIB database does not contain any information for the Rajant devices

The Rajant devices do not have MIB-II mgmt. information embedded to be able to provide information to Solarwinds, and for Solarwinds to perform an automatic discovery of the devices

The Rajant device use SNMP version 2 with a community string of public. This is not changeable

As result of these restrictions, adding a Rajant device to Solarwinds NPM is a manual process, which this document will cover and show how it is done.

The Rajant enterprise OID is iso.org.dod.internet.private.enterprises.rajantCorporation (1.3.6.1.4.1.34861), which we will be using to create custom pollers for the devices

Procedure

Phase 1

Adding the Rajant device to Solarwinds NPM

The Rajant device will be added to the Solarwinds NPM, either by means of a manual entry or a network discovery. In both instances the devices will be added via ICMP only and not via SNMP as the SNMP poll to the device will fail. One the device has been added the polling method will need to be changed manually to SNMP for every Rajant device on the network.

 

Adding a device manually

  1. Add device by clicking settings > Add a Node 20140618 15.10.01_Capture.jpg
  2. Type the IP address of the device in the IP address field
  3. Select the polling method to Status Only: ICMP
  4. Click Next 20140618 15.50.31_Capture.jpg
  5. Rename the device to something meaningful if necessary
  6. Click OK, ADD NODE
  7. Click OK after the device was added 20140618 15.52.46_Capture.jpg
  8. In node management, find the device that was added and select the checkbox
  9. Click Edit Properties 20140618 15.56.42_Capture.jpg
  10. Change polling method to SNMP
  11. Check SNMP version and port are correct and tick “Allow 64 bit Counters”
  12. Type in public in the community string field
  13. Click submit
  14. Click OK on the error dialog when the credentials are not validated 20140618 16.00.09_Capture.jpg
  15. Adding of the Rajant device is now complete

Phase 2

Adding Specific Pollers

The Rajant device has now been added to the Solarwinds application, which will be able to provide availability stats only, and show up and down time. For more advanced statistics, one would need to add Universal Device Pollers, specifying an OID to poll to provide these stats.

In this example we will add the device serial number. In order for us to be able to do this, we will need to know which OID will provide this information. In the rajant-mib file, each OID is described with regards to what information will be provided when polled. In this case we will use 1.3.6.1.4.1.34861.1.1 to get the serial number of the device as per the rajant-mib file

 

system OBJECT-IDENTITY

STATUS        current

DESCRIPTION   "System status"

::=  { rajantCorporation 1 }

 

serialNumber  OBJECT-IDENTITY

STATUS             current

DESCRIPTION        "Hardware serial number"

::= { system 1 }

 

To add a universal device poller, one will need to work directly on the server where the application was installed and use the universal device poller application

 

Adding a universal device poller

 

  1. Open the universal device poller application in the Solarwinds program group
  2. The application will then open
  3. Click on “New Universal Device Poller” and wait for the dialog box to come up 20140619 10.22.48_Capture.jpg
  4. In the OID field type in the OID for the specific statistic that information is required for 1.3.6.1.4.1.34861.1.1
  5. Provide a name for the poller
  6. Provide a description for the poller
  7. Click advanced options
  8. Set MIB value type to Raw Value
  9. Set Format to Text
  10. Set SNMP get type to GET
  11. Set Polling type to Node
  12. Click Finish 20140619 10.33.08_Capture.jpg

 

Phase 3

Assign the poller to the added device

  The specific poller has been added to Solarwinds NPM, and in order for it to be used, it needs to be assigned to a device or multiple devices.

 

Assigning a poller to a device

 

  1. Click on Assign Pollers and select the poller to use and click next 20140619 10.53.13_Capture.jpg
  2. Find and select the device to assign the poller to and click finish. To find the device easier, the “Group by” dropdown option may be used 20140619 10.56.13_Capture.jpg
  3. The poller is now assigned and the information will be presented on the node details in Solarwinds 20140619 10.59.17_Capture.jpg

 

CLOSURE

This concludes the procedure on adding a Rajant device to Solarwinds; however, this procedure may be used for any device that is known to have their own specific MIB file and is not limited to Rajant only.

To add more pollers for specific statistics, Phase 2 and Phase 3 need to be repeated, and the Specific OID will be provided for in the Rajant MIB file

rajant-mib

 

--

-- Rajant BreadCrumb MIB

--

RAJANT-CORPORATION-MIB DEFINITIONS ::= BEGIN

 

--

-- Import well known definitions from standard MIBs

--

IMPORTS

   MODULE-IDENTITY, OBJECT-IDENTITY, enterprises, OBJECT-TYPE, Unsigned32, TimeTicks, IpAddress, Integer32, Counter64

      FROM SNMPv2-SMI;

 

--

-- MIB meta data

--

rajantCorporation MODULE-IDENTITY

LAST-UPDATED   "201308200000Z"

ORGANIZATION   "Rajant Corporation"

CONTACT-INFO   "Omitted"

DESCRIPTION    "Rajant Corporation MIB"

 

--

-- Rajant's unique Enterprise ID (OID)

--

::= { enterprises 34861 }

 

system OBJECT-IDENTITY

STATUS         current

DESCRIPTION    "System status"

::=  { rajantCorporation 1 }

 

instamesh OBJECT-IDENTITY

STATUS         current

DESCRIPTION    "Instamesh status"

::=  { rajantCorporation 2 }

 

wireless OBJECT-IDENTITY

STATUS         current

DESCRIPTION    "Wireless interfaces"

::=  { rajantCorporation 3 }

 

serialNumber   OBJECT-IDENTITY

STATUS               current

DESCRIPTION          "Hardware serial number"

::= { system 1 }

 

systemTemperature    OBJECT-IDENTITY

STATUS               current

DESCRIPTION          "System temperature"

::= { system 2 }

 

freeMemory     OBJECT-IDENTITY

STATUS               current

DESCRIPTION          "Free memory"

::= { system 3 }

 

idle           OBJECT-IDENTITY

STATUS               current

DESCRIPTION          "Idle"

::= { system 4 }

 

uptime         OBJECT-IDENTITY

STATUS               current

DESCRIPTION          "Uptime"

::= { system 5 }

 

instameshArpDropped        OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of dropped ARP requests"

::= { instamesh 1 }

 

instameshArpRequests       OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of ARP requests"

::= { instamesh 2 }

 

instameshArpRequestsAnswered     OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of answered ARP requests"

::= { instamesh 3 }

 

instameshArpRequestsUnicasted    OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of unicast ARP requests"

::= { instamesh 4 }

 

instameshArpTotal          OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of all ARP requests"

::= { instamesh 5 }

 

instameshFloodsDropped           OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of dropped flood packets"

::= { instamesh 6 }

 

instameshPacketsDropped          OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of dropped packets"

::= { instamesh 7 }

 

instameshPacketsMulticast  OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of multicast packets"

::= { instamesh 8 }

 

instameshPacketsReceived   OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of received packets"

::= { instamesh 9 }

 

instameshPacketsSent       OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of sent packets"

::= { instamesh 10 }

 

instameshSourceFloodsDropped     OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Number of dropped source flood packets"

::= { instamesh 11 }

 

instameshTimeWaited        OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Time spent on waiting"

::= { instamesh 12 }

 

-- Wireless interfaces

-- The code below needs some serious refactoring

 

wlan0 OBJECT-IDENTITY

STATUS         current

DESCRIPTION    "Wireless interface wlan0"

::=  { wireless 1 }

 

wlan0name                  OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Interface name"

::= { wlan0 1 }

 

wlan0frequency             OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Operating frequency"

::= { wlan0 2 }

 

wlan0noise                 OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Noise level"

::= { wlan0 3 }

 

wlan0channelActiveTime           OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel active time"

::= { wlan0 4 }

 

wlan0channelBusyTime       OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel busy time"

::= { wlan0 5 }

 

wlan0channelReceiveTime          OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel receive time"

::= { wlan0 6 }

 

wlan0channelTransmitTime   OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel transmit time"

::= { wlan0 7 }

 

wlan1 OBJECT-IDENTITY

STATUS         current

DESCRIPTION    "Wireless interface wlan1"

::=  { wireless 2 }

 

wlan1name                  OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Interface name"

::= { wlan1 1 }

 

wlan1frequency             OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Operating frequency"

::= { wlan1 2 }

 

wlan1noise                 OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Noise level"

::= { wlan1 3 }

 

wlan1channelActiveTime           OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel active time"

::= { wlan1 4 }

 

wlan1channelBusyTime       OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel busy time"

::= { wlan1 5 }

 

wlan1channelReceiveTime          OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel receive time"

::= { wlan1 6 }

 

wlan1channelTransmitTime   OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel transmit time"

::= { wlan1 7 }

 

wlan2 OBJECT-IDENTITY

STATUS         current

DESCRIPTION    "Wireless interface wlan2"

::=  { wireless 3 }

 

wlan2name                  OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Interface name"

::= { wlan2 1 }

 

wlan2frequency             OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Operating frequency"

::= { wlan2 2 }

 

wlan2noise                 OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Noise level"

::= { wlan2 3 }

 

wlan2channelActiveTime           OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel active time"

::= { wlan2 4 }

 

wlan2channelBusyTime       OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel busy time"

::= { wlan2 5 }

 

wlan2channelReceiveTime          OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel receive time"

::= { wlan2 6 }

 

wlan2channelTransmitTime   OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel transmit time"

::= { wlan2 7 }

 

wlan3 OBJECT-IDENTITY

STATUS         current

DESCRIPTION    "Wireless interface wlan3"

::=  { wireless 4 }

 

wlan3name                  OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Interface name"

::= { wlan3 1 }

 

wlan3frequency             OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Operating frequency"

::= { wlan3 2 }

 

wlan3noise                 OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Noise level"

::= { wlan3 3 }

 

wlan3channelActiveTime           OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel active time"

::= { wlan3 4 }

 

wlan3channelBusyTime       OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel busy time"

::= { wlan3 5 }

 

wlan3channelReceiveTime          OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel receive time"

::= { wlan3 6 }

 

wlan3channelTransmitTime   OBJECT-IDENTITY

STATUS                     current

DESCRIPTION                "Channel transmit time"

::= { wlan3 7 }

 

END


Viewing all articles
Browse latest Browse all 1956

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>