Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

NetCool integration w/ Solarwinds

Has anyone integrated NetCool w/ Solarwinds. I'm having problems where the traps forwarded from Solarwinds are either dropped or delayed on the probe from NetCool's end. I wanted to get an idea of the default MIB provided by Solarwinds was ever re-written for NetCool.

Find more posts tagged with

Accepted answers

All comments

skirven

I am actually trying to go through the same exercise right now.

I am looking at raw traps that are going to Mercury/HP's Sitescope product and I'm not seeing where it's doing variable subsitution. I'm simply trying to debug the traps being sent over before trying to send them into NetCool.

17:02:32 07/06/2007 from=xx.xx.xx.xx:162 oid= n/a trap= n/a specific= n/a traptime=n/a community=public agent=xx.xx.xx.xx version= v2c var1=0 var2=1.3.6.1.4.1.11307.10 var3=1.3.6.1.4.1.11307 var4=<Node Name goes here> var5=255.255.255.255 var6=${SystemName} var7=${ObjectType} var8=8285 var9=${PropertyName} var10=${PropertyValue} var11=

What I'm not able to get out of this is the EVENT. (i.e. Interface down).

Does anyone have any templates used to send traps over that would have something like
- Interface Name
- Event Message

Ultimately, we would need to send this information over to NetCool, so maybe I'm not going to be able to use Sitescope to see the traps?

Thank you!
Stephen

dwong

Hi Stephen,

I was working w/ support and found out that the MIBs are too generic via Solarwinds. I have requested them to update the MIBs so that they would accept traps. As of now the mib to rules file via NetCool will need to manually be updated for each alert created as different variables are being utilized for different alerts. Hope this helps.

-Dana

skirven

Dana,
I tend to agree the integration is not there as I would have hoped. I ended up getting it to "work" by sending a SysLog event back to the SysLog service, and then having that send the trap over, and I was able to set up the traps as I needed to and they were interpreted well enough to create the rules in NetCool.

I feel as though the user should be able to create a SNMP Trap Alert right from Orion and then into NetCool. Unfortunately, the SNMP Alert feature is horrbily lacking native in Orion.

Thank you for your update,
Stephen

pblatz

We have Traps going to NetCool as follows.

1. Modifed the trap being sent to Netcool, Using the customize Trap tool. Here is our alert trap. Placement of the file depends upon version 7 or 8 of Orion. I also use the Beta Alert Engine on my ver 7 installation so the trap file is in both the NPM and the Common directory.

2. Create a custom rule file on Netcool.

Here is the NetCool Rules file

#####
# SolarWinds include file
######
# 02-MAR-2006; LPB:     Rules file created
#
# 10-MAR-2006; LPB:     @Identifier changed to @Node + $5 (ObjectType) + $6 (Obj
ectID)
#                       Added @URL field
#                       Added @Type field to allow changes for automation
#
# 14-MAR-2006; LPB:     Added @EscFields for ITSM handling
#
# 27-MAR-2006; LPB: Modified order of @EscFields
#
#######
# Seting $Variables from recieved OIDs
#
        $Severity = $1
        $Node = $2
        $IPAddress = $3
        $SysName = $4
        $ObjectType = $5
        $ObjectID = $6
        $PropertyName = $7
        $PropertyValue = $8
        $Status = $9
        $EventMessage = $10
        $LocRegion = $11
        $LocCountry = $12
        $LocBuilding = $13
#
# Set Netcool Fields
#
        @Agent = "SolarWinds"
        @Node = $Node
        @Severity = $Severity
        @EscField01 = @Agent
        @Summary = "Node Status: " + @Node + " is " + $Status
        @AlertGroup = "SolarWinds"
        @Identifier = @Node + $ObjectType + $ObjectID
        @URL = "http://w3mkborn01.mkcorp.com/NetPerfMon/view.asp?view=" + $Objec
tType + "Details&NetObject=" + $ObjectID
        @EscField02= @Severity
        @EscField06= @Node
        @EscField03= $LocRegion
        @EscField04= $LocCountry
        @EscField05= $LocBuilding
@EscField07= $PropertyName
        details($*)
#
# Case Statements
#