Kaseya Community

SNMP outside local network

This question is not answered

Hello

Is there a way to monitor machines with SNMP outside the local network.

All Replies
  • Yes it is called SNMPTrap its a new feature only available in K2, its very hard to figure out (for me anyways).

    Here is the doc I made on it earlier this year;

     

    Kaseya SNMP Trap configuration
    The goal of this document is to help you setup SNMP Trap monitoring via Kaseya.

    Definitions
    Some definitions to help explain what I’m talking about;
    • “Probe Server” – This is the server that you will be using to receive the SNMP Trap events (not necessarily the kserver).
    • “Target network device” – this is the network device that you want to monitor and (once configured) will be sending SNMP Trap information via UDP port 162 to the “Probe Server”.

    Prerequisites
    • The “Probe Server” must be a Kaseya Agent Managed machine with Windows OS.
    • The “Target network device” needs to support SNMP Trap and will have to in some way be able to enable and configure the ANMP Trap feature. (e.g.: web console)
    • “Probe Server” should be able to talk to the target network device via port 162 (SNMP Trap port). If not check if anything might be blocking communication between the “Target network device” and the “Probe Server”. (You can use telnet or putty to confirm connectivity.)
    • Application event logging with the Warning event category checked must be enabled for a managed machine (aka Probe Server) using Agent > Event Log Settings.

    Setting up SNMP Trap Monitoring in 3 steps.

    (Step 1) – Enabling SNMP Trap
    Enable and configure the SNMP trap feature on “Target network device”. You can set the thresholds low at first to trigger alerts if you want to confirm that the monitoring is working.

    (Step 2) – Creating the Event Set

    1. From Kaseya under Monitor > Agent Monitoring > SNMP Traps Alert, create a new SNMP Trap Event Set that relates to the Traps you want to monitor.

    2. This is pretty much identical to Kaseya Event log monitoring. Use the Edit button on “<New Event Set>” to make a new Event set and give it a name. You can also import existing event sets from here (if only we had any).

    3. Next set the Source Filter to; “KaseyaSNMPTrapHandler” and the Event ID to; “100”. Initially you won’t know what to put into the Description Filter until you have received some alert so you will more than likely need to update/tweak this event set. Use the Add button to add this “catch all line” and close the “Edit Event Set” window.


    (Step 3) – Adding the SNMP Trapp Alert
    1. Now again from Kaseya under Monitor > Agent Monitoring > SNMP Traps Alert, select your method of alerting (Create Alarm, Create Ticket, Run Script, Email Recipients), I recommend Email initially.
    2. Next select the new Event set you created in Step 2 and select the “Error” event option. SNMP Trap Alerts also use the “Information” event option however if you want to minimize the number of false alerts you can skip it.
    3. Select your preferred “Alert when this even ...” option, I recommend “Alert when this event occurs once” initially and then you can tweak it later once you have confirmed that your Alerts are working.
    4. As per Kaseya’s help documentation you can “ignore the SNMP Community field. This option is not yet implemented.”
    5. Select the your “Probe Server” and apply the Event set using the “Apply” button.

    Post configuration
    Below is an example of what you can expect if your SNMP Trap configuration was successful.

    Code:
    Subject: [Probe Server Name] Application log generated Warning Event 100

    Log: Application
    Type: Warning
    Event: 100
    Agent Time: 2010-07-15 10:11:56Z
    Event Time: 10:10:26 PM 14-Jul-2010 UTC
    Source: KaseyaSNMPTrapHandler
    Category: None
    Username: N/A
    Computer: (Probe Server)
    Description: (Target Server Name) [UDP: [0.0.0.0]->[x.x.x.x]:-4643]: Trap , .1.3.6.1.2.1.1.3.0 = Timeticks: (104086555) 12 days, 1:07:45.55, .1.3.6.1.6.3.1.1.4.1.0 = OID: .1.3.6.1.4.1.20632.2.1.8, .1.3.6.1.4.1.20632.2.2 = INTEGER: 4

    If you still are have problems make sure that an application called “KSNMPTRAP” has been installed on your “Probe Server” you can do this by checking the Add and Remove Programs. You can also use some 3rd party free/trial utilities to diagnose if SNMP Trap communication is being sent from your “Target network Device”.

    iReasoning's Mib Browser
    http://ireasoning.com/download.shtml

    ManageEngine MibBrowser Free Tool
    http://www.manageengine.com/products...ser-free-tool/

    Please note that the top two tool’s SNMP Trap features will not work from the “Probe Server” while Kaseya’s “KSNMPTRAP” software is running in the back ground so you might want to run these from another computer.