Network Topology Mapper (NTM)
Network Performance Monitor (NPM)
Kiwi Syslog
Failover Engine (FoE)
Start Using FoE v6.7
| Latest Blogs | ||
Make The Most Of FoE | Most Recent / Popular KB's | ||
FoE Documentation | Whitepapers
| ||
FoE How To Articles | FoE Releases | ||
Troubleshoot FoE | What Are We Working On
| ||
|
| ||
Kiwi CatTools
Start Using Kiwi CatTools v3.9
| Latest Blogs | ||
Make The Most Of Kiwi CatTools | Most Recent / Popular KB's | ||
Kiwi CatTools Documentation | Whitepapers | ||
Kiwi CatTools How To Articles | Kiwi CatTools Releases | ||
Troubleshoot Kiwi CatTools | What Are We Working On
| ||
|
| ||
ipMonitor
Start Using ipMonitor v10.7 | Latest Blogs | ||
Make The Most Of ipMonitor | Most Recent / Popular KB's | ||
ipMonitor Documentation | Whitepapers
| ||
ipMonitor How To Articles
| ipMonitor Releases | ||
Troubleshoot ipMonitor | What Are We Working On | ||
|
| ||
Engineer’s Toolset
Firewall Security Manager (FSM)
Enterprise Operations Console (EOC)
Allow for modification of the web interface session timeout
Per Where can I adjust the dashboard timeout settings it would be handy to be able to configure the session timeout for the alert central dashboard interface on a user by user basis. I believe the setting is currently available in the OS as the session-timeout variable in /opt/apache-tomcat/webapps/ROOT/WEB-INF/web.xml.
New to SolarWinds NPM & interested in improving reporting?—We want to talk to you!
The SolarWinds UX (User Experience) team is looking for people who have only been using SolarWinds NPM for 6 months or less who are interested in spending an hour with us to get a sneak peek at some revised design ideas for reporting on the web.
If you have used NPM for 6 months or less and have an hour to give us between 7am and 11am Central Tuesday, June 25th to Thursday, June 27th, we want to hear from you! Not only will you get an opportunity to influence future development of NPM, you will also get 2,000 points in the thwack store which you can use to buy t-shirts, caps, and other SolarWinds swag.
Don’t worry if you’re not the most sophisticated users on thwack. We’re really looking for noobs for this, so if that’s how you would describe yourself (as long as you’re someone who would be creating reports as part of your job), then we want to talk to you!
To sign up or learn more, contact kellie.mecham@solarwinds.com directly by sending me a private email. Thanks!
Where can I adjust the dashboard timeout settings
I am getting a little tired of walking away from my desk, looking at another tab or screen, or doing something that doesn't involve actively poking around the Alert Central dash constantly and then having to log right back in. is there a way to set the timeout longer than 5 minutes?
network goes down every 3 weeks
hi guys
i'm experiencing an issue that happens every 3 weeks for the last year, the users internet connection goes down until you reboot the core switch then it is ok for the next 3 weeks until it happens again, I have noticed that the uplink interface from the lan to the router receives lots of errors and discards that keep increasing daily could this be related, if so what could they be?
thanks in advanced
Matt
disk monitoring with mount points
thanks
Dennis
Login screen in report email
I have a weekly "Interface Percent Utilization Report" sent to one of my customers, however, the report URL link and the .PDF attachement just show the SolarWinds login screen and nothing more. When I run the report via the "Reports" tab, everything is fine. What is wrong with my email setup?
Thank you,
David
FoE and APE Scenaro across WAN question
Can anyone help me understand how FoE would perform in the following scenario?
We have our main polling engine in our UK data center, and an additional polling engine (APE) in the United States.
We plan in installing FoE so that the UK server is the active primary, and the APE in the US is the passive failover system.
Question: What happens when the US to UK WAN link is down?
(A) if the main polling engine is functional, will it continue to poll nodes on it's side of the WAN link?
(B) if the WAN link does down, and THEN the main polling engine crashes...how will the passive failover know to take over?
Thanks for your help/advice on this.
Add Service Manager functionality to the Web Access
With SolarWinds moving to a new web server and offering AD Authentication, it would be nice to have some
of the functionality available at the server console via the Service Manager.
Some things that come to mind:
Ability to configure and setup rules
Change from the "Events" Tab to "Displays" and be able to switch between "Displays" on the web
Get Statistics.
Ability to log Statistics to a database for reporting purposes.
Ability to configure and run reports.
I know that those last two items aren't current out of the box features in the Service Manager either,
but someone got me thinking about what I would want out of this software if I was brand new to it and
did not feel comfortable with scripting.
I would want more out of the web interface for sure and the ability to run reports
on the events logged and being able to see real-time statistics is important to me as well. But I feel these
things along with the configuration capabilities of the Service Manager should be available remotely via the
Web Access.
Use SNMP-based Tools Carefully, Or They Can Turn Against You
SNMP is a wonderful, sometimes maddening management protocol. It can provide monitoring, powerful trending, and alerting when things go wrong on the network. But too much of anything can be bad, and SNMP is no exception. When not properly managed, SNMP itself can become problematic.
Most seasoned network admins buy into basic best practices like disabling SNMP when not in use on host devices, changing strings occasionally, and using ACLs to control who can use SNMP so resources like router CPUs don’t get DOS’d by the very protocol meant to manage the environment.
But sometimes other SNMP-related issues creep in when we get sloppy. It’s easy for multiple admins to set up eval copies of SNMP-based config management or monitoring software without coordinating the polling cycles of each. Or to perhaps set up a special monitoring instance that’s meant to use SNMP to help pinpoint some specific problem, without implementing common-sense safeguards (like we don’t want to SNMP-read our core routing tables every 10 minutes). Worst, these tools are easy to put in place and forget about, which means our SNMP traffic can get out of hand and become problematic.
Is your own SNMP house in order?
Does Anybody Actually Use the CLI?
An observation I have made over the years is that during acquisition of a storage, network, or computing system in general, most storage and system administrators I know seem to care deeply about having a command-line interface, or CLI. Once the system is acquired, though, they never use it, preferring to use the graphical user interface exclusively.
What gives? Is this just a way to torture vendors during the acquisition process, or is there something inherently wrong with a CLI? Do we only care about the CLI because of some idea in our heads that we’re going to do greater things with it (or perhaps via it), and we should be more realistic? Or do people actually use CLIs and I’m just looking at an unrepresentative sample of the world of IT?
InterfaceName property
I'm trying to use this code snippet to loop through the VLAN interfaces on routers to change IP Helper addresses. The problem is that the InterfaceName property includes a dash in the name so you can't use it in a script.
For example It returns VLAN-10 instead of VLAN10
Anyone have a work around? I need to get this script working for a couple hundred switches before the weekend change.
Thanks!
// Loop through selected interfaces
foreach (@interfaceItem in @ContextNode.Interfaces)
{
if (@interfaceItem.InterfaceName contains 'VLAN')
{
CLI
{
interface @interfaceItem.InterfaceName
}
CLI
{
ip helper-address 10.0.252.10
ip helper-address 10.0.252.11
no ip helper-address 10.101.6.158
no ip helper-address 10.101.6.159
no ip helper-address 157.142.8.10
}
CLI
{
exit
}