This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

RAJANT Breadcrumbs (LX4 and ME4)

Hi Everyone,

Does anyone have experience in monitoring RAJANT Breadcrumb devices using SolarWinds? The devices do seem to have SNMP enabled and they have a MIB for snmp, but I was unable to import that information into SolarWinds. Any help would be appreciated.

Regards,

Simon

  • Depending on the supported MIBs (I didn't find any information in a quick search) you may need to create a custom CPU / Memory poller via "Manage Pollers" or some UnDPs. http://www.solarwinds.com/resources/videos/universal-device-pollers-undp-solarwinds-training-network-performance-monitor.html

  • Thanks Rob - as a matter of interest here is the MIB for the rajant as supplied by them.

    --
    -- 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 "Marty Lamb (mlamb@roinet.com)"
    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

  • Hi simonlindsay

    This is something that we are also interested in.

    I had a meeting with a Rajant representative a few months back and they advised that they do not currently use SNMP to monitor their devices as it adds a lot of overhead on the MESH bandwidth.

    They advised using something like Cacti which could be used to integrate with the Rajant API, hopefully they will expand their SNMP capabilities soon.

  • Hi There,

    Yeah their product is called RRADS, and runs on Linux, so does Cacti, but to get it running is a massive mission, there is a way to get it running under Windows, but you need MySQL, PHP and some bits of code, it's ridiculous. I have also had discussion with Rajant in the US and they say that a windows based reporting tool is on the radar for development but is not a big priority based on the current requirement. The Rajant devices have SNMP capabilities on the newest firmware version (11.5.0), and the mib exists, so I'm sure someone in the forum could assist in getting this MIB working with SolarWinds?

    Where are you based by the way?

  • Hi

    Would be cool to integrate into Solarwinds, specifically looking at the What We're working on pagep ost 10.7. "Wireless Heatmaps - view observed and calculated signal strength and client location"

    Anyways, I am based in South Africa.

  • Hi,

    I see this is an old post, nevertheless, I am using Solarwinds/rajant in conjunction with each other.

    I refer you to a video I made in setting it up.... https://www.youtube.com/watch?v=FzOyIoonx-0

    Also a document as explanation... Adding a Rajant device to Solarwinds NPM

    Let me know if it helps