RichardLetts ✭✭✭✭✭

I uses to use this, but now I get: High Risk Website Blocked Access has been blocked as the threat Mal/HTMLGen-A has been found on this website.

Solarwinds does allow duplicate nodes with the same IP address when you have multiple pollers -- you have to have them on different pollers, but it works.

right, the challenge, with DWDM nodes is that the MIB indexes variables on the optical path may not have equivalents in the ifMIB. This makes it a challenge to tie optical power readings and optical signal presence to an interface: With the cisco ONS MIB it would have been so much easier if they had created ifMIB entries…

we're running in that configuration

NPM needs the reports directory as well.

I don't think this is right (the CAL licencing count) you will need a CAL for each solarwinds user as well if you go that method. SolarWinds Knowledge Base :: What kind of SQL Server licensing does SolarWinds require?

case# ? a co-worker is about to start our 11.5.1 upgrade (we have a large number of other open cases waiting on upgrading so it would be good to know this in case we hit the same problem)

I wish the release notes included a version history with what is new in this version. 11.0.1 release note chnages: Support for MS SQL Server 2012 SP2 You may upgrade directly to this version of SolarWinds NPM from NPM version 10.4 or higher. (11.0.0 could be upgraded from 10.3)

aside: SWO doesn't need the MIB to be loaded to interpret the SNMP traps; we use SNMP traps internally and it works fairly well. Fortunately since the Trap receiver doesn't interpret received trap mibs correctly anyway, it's useful that it doesn't rely on the MIB to decode the trap. 1.3.6.1.4.1.150.16000.1.0.1…

upvote the idea here: http://thwack.solarwinds.com/ideas/1952

upvote the idea here: http://thwack.solarwinds.com/ideas/1952 being able to set this has not garnered as many votes as other ideas

I run it 10 times when only upgrading one module... And because a Solarwinds developer decided that making database changes in the additional polling engine wizard was a good idea you can't run it on multiple servers simultaneously.

last try (NPM 10.6) try this (for an alert on a node) ${SQL:Select MAX(MsgId) from AlertLog where AlertDefId='${AlertDefId}' and message='Alert Triggered' and ObjectId=${NodeID}}

You might have more luck asking in the DPA or SAM forum,

What steps did you perform to get to this place? If you installed 10.1.3 on your new database and then tried to restore over it then I would expect it to fail because the schema do not match. The Application upgrade/install process includes steps that migrate the contents of your database to the new schema the PDF document…

note: when you upgrade the product the polled OID is the unique key. some of the 'example' UnDPs are somewhat useful for APC ups, and so they all get moved from my 'APC' folder into 'Example' which is annoying.

that looks good, Note, I don't understand the traps in this case... I'm going to have to guess in the stuff below If you want to have separate alerts for each BUSCODE (is that the type of error?) then you might have to join with the trapvarBinds table. If you use the queries you have below then you get ONE alert type per…

CP values? really? Your devs need to read: xkcd: Exploits of a Mom

Awesome :-( I've moved jobs to a cisco shop, and will be tackling this very issue in the next few months... i.e. redundant controllers, solarwinds, and cisco Prime... I was hoping this would not be a problem in this environment... so if Solarwinds can fix it for us, they will also fix it (probbaly) for Aruba.

I make use of external nodes for BGP peers -- I can assign IP addresses to them to grok which peer has gone down. I'm thinking of using them to represent APs and a little bit of SQL code so I can manage Thin Access points as if they were nodes, because the current Thin Access point management is non-existent.

[well, DUH on me for not including this] NCM: 7.2.1 / NPM: 10.6.1 / UDT 3.1.2: + a whole load of buddy drops

(this is from our 'routine duties of the NOC' page, and there are hyperlinks to the actual instructions on each line)

here is my perl my $AddedNode=$swis->Create('Orion.Nodes', {'Caption'=>$ip ,'IPAddress'=>$ip ,'IPAddressguid' => ip2guid($ip) ,'DynamicIP'=>'false' ,'UnManaged'=>'false' ,'EngineID'=>1 ,'Status'=>1 ,'Allow64BitCounters'=>1 ,'ObjectSubType'=>'SNMP' ,'SNMPVersion'=>2 ,'Community'=>$rocid ,'SysObjectID'=>$oid…

see the NPM RC thread -- there is a fix there that worked for us: * Please navigate to c:\Program Files (x86)\SolarWinds\Orion * Locate the file SWTrapService.exe.config * Locate <add key="UseCollectorEndpoint" value="True"/> * Change "True" to "False" * Save the file. * Load orion service manager found under start >…

I'm taking the opposite view: because solarwinds currently does nothing with Traps wrt alerts -- see all of the posts I have made on using cusom SQL to generate alerts from traps I find it very useful to look at the unusual MIB traps coming in like this: Note, the way APC does traps is via the SNMPv1 to snmpV2 transition…

I'm sure that many people would like to help but you have not followed the standard litany: FGA: Please follow the standard litany when giving a problem report. a) what does your code look like; post the actual code b) what makes you think it is sending what you think it is to the solarwinds server; have you run…

(the SSG are about the only series of Juniper devices we don't have so I don't exactly know) In order to get this work you probably have to monitor both the Interface and the Unit (at least this is what is needed with Juniper/JunOS EX series switches) this is because the error counters are on the interface, and the L2 MAC…

as an aside jnxVirtualChassisMemberTable has some more interesting variables, e.g. jnxVirtualChassisMemberSerialnumber jnxVirtualChassisMemberRole jnxVirtualChassisMemberMacAddBase jnxVirtualChassisMemberSWVersion jnxVirtualChassisMemberPriority jnxVirtualChassisMemberUptime jnxVirtualChassisMemberModel…

on trap, invoke a perl script with the Nodeid and IP address if the nodeid is zero (an unknown node) the create a discovery for the node, looking at examples from here: Perl SDK - Start Discovery - PluginConfigurations then you can manage what you like from the discovery....

Please add the ability to create alerts on a PORT (generically) to the alert managers e.g. Select PortID, Name from UDT_Port Richard