Comments
-
Do you want to reboot the machines manually or when a certain event happens?? Why not just use something like shutdown.exe which is built into 2K/XP?? If you want to trigger a reboot upon a certain event you could use a Solarwinds event to run the shutdown executable. You could pass the machines IP address using the…
-
I've heard mention of SNMP v3 being supported in Orion 8....when that happens to be released though, who knows.
-
Set appropriate NTFS permissions on OrionNetPerfMon.exe
-
Rather than scripting a telnet session which i've found to be flakey in the past with delay timings for the keystrokes, use something like PSTools utility PSEXEC to launch the .bat directly remote box.
-
On each of the graphs, click edit resource and enter unmanaged=0 in the filter box.
-
If it's a Windows box you need to install and configure SNMP. Install SNMP on the PC via control panel, add/remove programs, windows components. Once installed, configured SNMP via control panel, services. The settings are made in the properties of the SNMP service.
-
Yes. When adding a node just put a tick in the box for 'node does not support SNMP' and it'll just monitor response time and packet loss.
-
Not at the moment. Talked about here and heard possible inclusion in V8 but as usual no roapmap/featurelist from the SW guys so who knows.
-
I've not had this myself or tried to replicate the issue but i'm sure on a per map basis there is an option to hide nodes the user doesn't haev rights to view. OK, it won't stop them seeing the map and it's background but there will be no nodes on the map that they're not allowed to see.
-
Spoke to support today and looks like a possible bug in the 7.7 Syslog program. Went through a few things and still no filter working. Was sent an updated version and hey presto..works a treat. Thanks to Eric at SW support!
-
Just tried using the rule suggested by BK, and we're still logging messages with source 10.98 and 10.22 with dest port of 137.
-
Apologies again... The particular syslog message i posted did contain src=10.98 and i mentioned 10.22. I have 2 rules, one for 10.98 and one for 10.22. I can't use 10. as there are other 10. subnets which we don't want to exclude. I actually use 2 rules, one for 10.98 and one for 10.22 I'm sure i did initially try…
-
I read the post back and maybe didnt phrase it correctly (ok, pretty poorly)...quote:The rule i'm trying to implement is drop all traffic from source 10.22. with dest port 137. What i meant to write was, i'm trying to implement a rule to drop all syslog messages that containing src=10.22 and dst_port=137. The long and…
-
quote:Originally posted by aSquared Sidetrack a little. Has anyone here overcome the issue of ORION not able to monitor Service ports. Do you have any alternatives to this? I'm certain i read/heard something about an Orion Application Monitor... Does anyone else have any info of help...does this exist/how do we get it/what…
-
Normally if the port is up and there's no mac address it's because the connected device isn't powered on.
-
I thought the same... We want to install aswell but the eval is only SL200 so we can't even use that for 30 days until they sort out the keys.
-
Pretty much as above but use an ACL to prevent unauthorised access access-list 1 permit xx.xx.xx.xx snmp-server community communitystring R0 1
-
quote:Originally posted by josh@solarwinds.net With regards to Custom MIBs, I'm wondering which MIBs that people are most interested in monitoring. Which ones are you interested in? We're missing CPU/Memory usage from all our HP Procurve 8000 switches and Fortigate 800 firewalls. Would be really great if we could get that…
-
The Network Services pack sounds interesting... Are you able to say what features can we expect from this module?
-
Considering we've all paid maintenance it's pretty poor Solarwinds offer no roadmap or at least any indication of timescales for new versions/features. We certainly won't be renewing maintenance again until v8 is actually released.
-
Check that the messages are originating from the same IP that you use to monitor the node with. On some of our devices with multiple interfaces we had to use the logging source-interface interface command to set the source IP the same as our Solarwinds node IP.
-
I presume when a switch fails, this would be seen in the log. If that's the case, you could output the logs via syslog and alert on that.