Why is it taking so long to speak to a support person?
I tried to speak to someone yesterday and waited an hour without speaking to someone.
I am trying again today.
Why is it taking so long to speak to a support person?
I tried to speak to someone yesterday and waited an hour without speaking to someone.
I am trying again today.
Good morning!
I'm trying to build a view that will display the 'Average bits per second (Step Chart)' for a couple different interfaces in a single place. I've poked around and found a handy thread where folks had done something like this for the classic charts, but is it possible to do the same for the 'new' charts? The classic charts leave much to be desired.
When I input the following into my Custom HTML resource, all I get back is a busted image icon instead of the chart I'm after:
<img src="/Orion/Charts/CustomChart.aspx?view=InterfaceDetails&ResourceID=466&NetObject=I%3a2846" />
But I can take that same link, add my Orion server to the beginning (https://orion-server/) and drop it into Chrome/Internet Explorer and get the chart I'm looking for. Thoughts?
Good afternoon,
I am wondering if there is a way to monitor a static route, and if any traffic traverses the static route. I'm familiar with the "Network Performance Monitor", is there anything similar to this? Like a route perf mon?
I am being tasked with implementing a dynamic routing solution, so I will need to find out which statics are being utilized, and the ones I can phase out of the environment.
Thanks and have a great day!
have a question on snmp traps. I am receiving traps and i can show off on the console. But, want to register as an event when a trap comes with some specific value. is it possible?
Hi,
I'm planning to upgrader my NPM from 12.1 to 12.2.
my SQL database is running on SQL server 2008 and as you now NPM 12.2 doesdn't accept it anymore.
I will move the SQL database to a SQL server 2014.
Did anyone do this? any tutorial for how to stop NPM services, backup/restore the DB on the new server?
Thank you.
Additional System info at the end:
Win2016 OS, VMWare, SW SQL DB native to the box
64GB RAM, 750GB 'Logs' drive, 8 CPUs
SQL2017
I have a few issues that pop up on the Active Diagnostics window. Some have already been addressed per the KB articles that are attached to the logs but still show up, others just won't run. Any ideas would be fantastic! I've already tweaked down all the retention periods and expanded out a little bit the polling rates.
Here is something that constantly comes up in the check, but I've done everything in the KB article. To note, SQL2017 already comes with support for TLS 1.2, and Server2016 should already have TLS 1, 1.1, and 1.2 enabled:
Check if TLS 1.0 is enabled on SQL server
RESULT: Failure
DURATION: 00:00:02.3597427
DISCOVERED: 3/16/2018 12:46:45 PM
RESOLUTION: Please enable TLS 1.0 protocol on this machine and rerun the test. Alternatively you can install latest TLS 1.2 updates for SQL Server. See KB MT96796. (Ran through all these steps, added in the requisite keys, reboot several times)
DESCRIPTION: TLS 1.0 is disabled on this machine. (Not as far as I can tell)
I have yet to get this to run:
Check DB integrity errors
RESULT: Failure
DURATION: 00:02:00.0029293
DISCOVERED: 3/16/2018 12:51:46 PM
DESCRIPTION: Diagnostic timed out.
And this, I also ran through the KB, but it didn't seem to have an effect:
TOTAL CHILD RESULTS: 1
Check if Database Maintenance works properly
RESULT: Failure
DURATION: 00:00:01.3738685
DISCOVERED: 3/16/2018 12:46:42 PM
RESOLUTION: Try to run Database Maintenance again after closing all applications that use related log file including Database Maintenance window. If this didn't help you could try to run Database Maintenance after moving its log files to another folder. See KB MT99308.I can't run DB Maintenance, the application throws a fail, no detail)
DESCRIPTION: There may exist certain issue with Database Maintenance log file.
Checking log file structure and log items format
RESULT: Failure
DURATION: 00:00:00
RESOLUTION: Try to run Database Maintenance again after closing all applications that use related log file including Database Maintenance window. If this didn't help you could try to run Database Maintenance after moving its log files to another folder.(I can't run DB Maintenance, the application throws a fail, no detail)
DESCRIPTION: There may exist certain issue with Database Maintenance log file.
Additional Information about the environment
Web Server | PHL-DU-DOSOL3 |
Software Version | Windows Server 2016 |
OS Version | 10.0.14393.0 |
Service Pack | |
Database Server | PHL-DU-DOSOL3 |
Catalog | SolarWindsOrion |
Database Engine | Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Aug 22 2017 17:04:49 Copyright (C) 2017 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor) |
SQL Version | Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Aug 22 2017 17:04:49 Copyright (C) 2017 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor) ; Product level : RTM |
Security Model | Integrated Security |
User Name | |
Connection Timeout | 20 |
Network Elements | 3047 |
Nodes | 553 |
Interfaces | 529 |
Volumes | 1965 |
Alerts | 424 |
Events | 882657 |
Pollers | 11171 |
Polling Engines | 1 |
Last Database Archive | 16-Mar-2018 01:15 AM |
Next Scheduled Database Archive | 17-Mar-2018 01:15 AM |
Database Archive Time | 01:15 AM |
Retain Detail Stats | 2 Days |
Retain Hourly Stats | 2 Days |
Retain Daily Stats | 30 Days |
Retain Container Detail Stats | 2 Days |
Retain Container Hourly Stats | 2 Days |
Retain Container Daily Stats | 30 Days |
Retain Events | 5 Days |
Retain Syslogs | 2 Days |
Retain Traps | 2 Days |
Server
Web Server | XYXYXYXYXY |
Software Version | Windows Server 2016 |
OS Version | 10.0.14393.0 |
Service Pack | None |
Total Count | 3047 |
Nodes | 553 |
Interfaces | 529 |
Volumes | 1965 |
AccountLimitationBuilder.exe | 2017.03 |
AlertManager.exe | 2017.03 |
AntiXSSLibrary.dll | 4.2.0.0 |
Antlr3.Runtime.dll | 3.5.0.2 |
ARSoft.Tools.Net.dll | 2.2.6.6 |
BouncyCastle.Crypto.dll | 1.7.5898.27424 |
Castle.Core.dll | 3.3.0.2287 |
Castle.Windsor.dll | 3.3.0.2439 |
ConfigurationWizard.exe | 2017.3.5300.1920 |
Database-Maint.exe | 2017.3.5300.1794 |
DatabaseManager.exe | 10001.1.1.10354 |
DotNetOpenAuth.Core.dll | 4.3.4.13329 |
DotNetOpenAuth.OAuth2.Client.dll | 4.3.4.13329 |
DotNetOpenAuth.OAuth2.ClientAuthorization.dll | 4.3.4.13329 |
DotNetOpenAuth.OAuth2.dll | 4.3.4.13329 |
EasyNetQ.dll | 0.54.3.424 |
EntityFramework.dll | 6.0.21010.0 |
EntityFramework.SqlServer.dll | 6.0.21010.0 |
EO.Base.dll | 16.0.55.0 |
EO.Pdf.dll | 16.0.55.0 |
EO.WebBrowser.dll | 16.0.55.0 |
EO.WebEngine.dll | 16.0.55.0 |
ExportToPDFCmd.Exe | 10001.1.1.243 |
Google.OrTools.dll | Unknown |
Google.OrTools.x86.dll | Unknown |
Google.Protobuf.dll | 3.3.0.0 |
HAEnableDisable.exe | 2017.3.1.3303 |
HtmlAgilityPack.dll | 1.4.6.0 |
HtmlSanitizationLibrary.dll | 4.2.0.0 |
ICSharpCode.SharpZipLib.dll | 0.86.0.527 |
Infragistics2.Shared.v7.3.dll | 7.3.20073.38 |
InstallHelper.RunOnce.exe | 2017.3.5320.1819 |
Interop.cdosys.dll | 1.0.0.0 |
Interop.COMAdmin.dll | 1.0.0.0 |
Interop.NetFWTypeLib.dll | 1.0.0.0 |
Interop.olelib.dll | 1.61.0.0 |
Interop.OrionSWScheduler8.dll | 1.0.0.0 |
Interop.SHDocVw.dll | 1.1.0.0 |
Interop.TaskScheduler.dll | 1.0.0.0 |
Kiwi_LogViewer_2.1.0_Win32.setup.exe | Unknown |
log4net.dll | 1.2.10.0 |
LogAdjuster.exe | 2017.3.5300.1794 |
makecert.exe | 6.1.7600.16385 (win7_rtm.090713-1255) |
Microsoft.Practices.TransientFaultHandling.Core.dll | 5.1.1209.1 |
Microsoft.Web.Services3.dll | 3.0.5305.0 |
MomConnectorFrameworkV2.dll | 5.0.2749.0 |
NetPerfMonEventLog.dll | 6.0.0.0 |
Newtonsoft.Json.dll | 6.0.8.18111 |
Ninject.dll | 3.2.2.0 |
nsoftware.IPWorksSSNMP.dll | 9.0.5077.0 |
OpenRabbitMQConsole.exe | 2017.3.5300.1794 |
OptimizeWebsite.exe | 10001.1.1.10117 |
OrionInstallerLib.dll | 10001.1.1.122 |
OrionInstallerProgressCounter.dll | 10001.1.1.122 |
OrionPermissionChecker.exe | 2017.3.5300.1920 |
OrionReportWriter.exe | 2017.03 |
OrionSWDiscoveryServices9.dll | 2017.03 |
OrionSWLogger.dll | 2017.03 |
OrionSWScheduler8.dll | 2017.03 |
OrionWeb.dll | 2017.3.5300.1920 |
phantomjs.exe | 1.9.2 |
PollerCheckerTool.exe | 2017.3.5300.1794 |
PrintLauncher.exe | 2017.3.5300.1794 |
RabbitMQ.Client.dll | 3.6.0.0 |
RegAsm.exe | 4.6.1586.0 built by: NETFXREL2 |
SciLexer.dll | 3.0.4 |
SciLexer64.dll | 3.0.4 |
ScintillaNet.dll | 2.5.0.0 |
SmartThreadPool.dll | 2.0.1.0 |
SnmpWalk.exe | 1.0.0.83 |
SolarWinds.Administration.Contract.dll | 1.1.0.2770 |
SolarWinds.AgentManagement.Contract.dll | 1.8.0.283 |
SolarWinds.Alerting.Service.exe | 2017.3.5300.1794 |
SolarWinds.ApiProxyFactory.dll | 1.0.0.36 |
SolarWinds.AssemblyResolver.dll | 1.0.0.37 |
SolarWinds.BusinessLayerHost.Contract.dll | 2017.3.5300.1794 |
SolarWinds.BusinessLayerHost.exe | 2017.3.5300.1920 |
SolarWinds.BusinessLayerHostx64.exe | 2017.3.5300.1920 |
SolarWinds.Collector.Contract.dll | 2.13.0.297 |
SolarWinds.Common.dll | 10001.1.1.10230 |
Solarwinds.Compression.dll | 10001.1.1.10140 |
SolarWinds.ConfigurationWizard.Common.dll | 2017.3.5300.1920 |
SolarWinds.ConfigurationWizard.IIS7.dll | 2017.3.5300.1920 |
SolarWinds.ConfigurationWizard.IIS7.Installer.exe | 2017.3.5300.1794 |
SolarWinds.ConfigurationWizard.Permissions.dll | 2017.3.5300.1920 |
SolarWinds.ConfigurationWizard.Plugin.APM.dll | 6.5.0.3680 |
SolarWinds.ConfigurationWizard.Plugin.CloudMonitoring.dll | 1.1.0.258 |
SolarWinds.ConfigurationWizard.Plugin.Common.dll | 2017.3.5300.1920 |
SolarWinds.ConfigurationWizard.Plugin.HA.dll | 2017.3.1.3303 |
SolarWinds.ConfigurationWizard.Plugin.NetFlow.dll | 4.2.3.4125 |
SolarWinds.ConfigurationWizard.Plugin.NetPath.dll | 1.1.1.4015 |
SolarWinds.ConfigurationWizard.Plugin.NPM.dll | 12.2.5300.360 |
SolarWinds.ConfigurationWizard.Plugin.OIP.dll | 2.8.0.196 |
SolarWinds.ConfigurationWizard.Plugin.Orion.dll | 2017.3.5300.1794 |
SolarWinds.ConfigurationWizard.Plugin.Recommendations.dll | 1.3.0.4759 |
SolarWinds.ConfigurationWizard.Plugin.SEUM.dll | 2.2.1.426 |
SolarWinds.ConfigurationWizard.Plugin.VIM.dll | 8.1.0.6436 |
SolarWinds.Data.Entity.dll | 2017.3.0.1061 |
SolarWinds.DatabaseManager.Strings.dll | 10001.1.1.10354 |
SolarWinds.DataGap.AnalysisTool.exe | 10001.1.1.291 |
SolarWinds.Dependencies.Strings.dll | 10001.1.200.10933 |
SolarWinds.Diagnostics.DBResponse.exe | 10001.1.1.348 |
SolarWinds.FipsManager.exe | 2017.3.5300.1794 |
SolarWinds.HighAvailability.Contract.dll | 2017.3.1.851 |
SolarWinds.HighAvailability.Utilities.dll | 2017.3.1.851 |
SolarWinds.InformationService.Contract2.dll | 2017.3.0.710 |
SolarWinds.InformationService.Linq.dll | 1.0.25.219 |
SolarWinds.InformationService.Linq.Plugins.Core.dll | 0.0.0.0 |
SolarWinds.InformationService.Linq.Plugins.HA.dll | 0.0.0.0 |
SolarWinds.Internationalization.dll | 10001.1.1.10182 |
SolarWinds.JobEngine.Contract2.dll | 2.11.0.313 |
SolarWinds.Licensing.Diagnostics.exe | 4.1.110.0 |
SolarWinds.Licensing.Framework.dll | 4.2.0.1685 |
SolarWinds.Logging.dll | 10000.1.1.73 |
SolarWinds.Management.dll | 10001.1.1.227 |
SolarWinds.MessageBus.Contract.dll | 1.3.0.37 |
SolarWinds.MessageBus.dll | 1.3.0.37 |
SolarWinds.MessageBus.RabbitMQ.dll | 1.3.0.37 |
SolarWinds.Net.ICMP.dll | 10001.1.1.10138 |
SolarWinds.Net.SNMP.dll | 10001.1.1.10263 |
SolarWinds.Net.WMI.dll | 10001.1.1.10242 |
SolarWinds.Netflow.Common.dll | 4.2.3.4125 |
SolarWinds.Netflow.FastBit.Client.dll | 4.2.3.4125 |
SolarWinds.Netflow.FastBit.Contract.dll | 4.2.3.4125 |
SolarWinds.Netflow.Installer.Common.dll | 4.2.3.4125 |
SolarWinds.Netflow.Installer.Core.dll | 4.2.3.4125 |
SolarWinds.Netflow.Strings.dll | 4.2.3.4125 |
SolarWinds.Netflow.Utils.dll | 4.2.3.4125 |
SolarWinds.NTM.Common.dll | 2.1.1.383 |
SolarWinds.NTM.Data.dll | 2.1.1.383 |
SolarWinds.NTM.Discovery.dll | 2.1.1.383 |
SolarWinds.NTM.Topology.dll | 2.1.1.383 |
SolarWinds.Orion.ActiveBackupStateStorage.dll | 1.0.1.40 |
SolarWinds.Orion.ActiveDiagnostics.Contract.dll | 1.7.0.396 |
Solarwinds.Orion.AssemblyResolver.dll | 10001.1.1.58 |
SolarWinds.Orion.Auditing.dll | 10001.1.400.898 |
SolarWinds.Orion.Batching.dll | 10001.1.1.520 |
SolarWinds.Orion.Channels.dll | 10001.1.1.582 |
SolarWinds.Orion.Collector.MessagePlugin.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Collector.Plugins.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Common.dll | 10001.1.1.10369 |
SolarWinds.Orion.CommonHelper.Interop.dll | 2017.3.5300.1794 |
Solarwinds.Orion.Composition.dll | 10001.1.1.58 |
SolarWinds.Orion.Configuration.dll | 10001.1.1.596 |
SolarWinds.Orion.Core.Actions.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Alerting.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Alerting.Plugins.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Auditing.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.BusinessLayer.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.CertificateUpdate.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Collector.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Collector.MessageSender.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Common.dll | 2017.3.5300.1920 |
Solarwinds.Orion.Core.Data.dll | 2017.3.5300.1794 |
Solarwinds.Orion.Core.Database.dll | 2017.3.5300.1794 |
Solarwinds.Orion.Core.Dependencies.dll | 10001.1.200.10933 |
SolarWinds.Orion.Core.Discovery.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Jobs.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Jobs2.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.MessageActions.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Models.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.Pollers.dll | 2017.3.5300.1920 |
SolarWinds.Orion.Core.Reporting.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Core.SharedCredentials.dll | 10001.1.1.477 |
SolarWinds.Orion.Core.Strings.dll | 2017.3.5300.1920 |
SolarWinds.Orion.Core.SwisViaCOM.dll | 2017.3.0.607 |
SolarWinds.Orion.Core.Topology.dll | 2015.2.0.200 |
SolarWinds.Orion.Discovery.Contract.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Discovery.Framework.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Discovery.Job.dll | 2017.3.5300.1794 |
SolarWinds.Orion.FeatureManager.Interop.dll | 2017.3.5300.1794 |
SolarWinds.Orion.FluentSqlClientProxy.dll | 1.0.1.236 |
SolarWinds.Orion.HighAvailability.Api.dll | 2017.3.1.3303 |
SolarWinds.Orion.HighAvailability.Auditing.dll | 2017.3.1.3303 |
SolarWinds.Orion.HighAvailability.Common.dll | 2017.3.1.3303 |
SolarWinds.Orion.HighAvailability.dll | 2017.3.1.3303 |
SolarWinds.Orion.HighAvailability.Strings.dll | 2017.3.1.3303 |
SolarWinds.Orion.I18n.Interop.dll | 1.0.0.0 |
SolarWinds.Orion.MacroProcessor.Contract.dll | 10001.1.200.1148 |
SolarWinds.Orion.MacroProcessor.DataFormatters.dll | 10001.1.200.1148 |
SolarWinds.Orion.MacroProcessor.dll | 10001.1.200.1379 |
SolarWinds.Orion.MacroProcessor.Strings.dll | 10001.1.200.1148 |
SolarWinds.Orion.Module.Common.dll | 10001.1.200.1164 |
SolarWinds.Orion.Module.Models.dll | 10001.1.200.1164 |
SolarWinds.Orion.Netflow.Logging.dll | 4.2.3.4125 |
SolarWinds.Orion.NetObjects.Models.dll | 10001.1.1.390 |
SolarWinds.Orion.NetObjects.Strings.dll | 10001.1.1.390 |
SolarWinds.Orion.Packages.dll | 1.0.0.729 |
SolarWinds.Orion.Pollers.Framework.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Proxy.I18N.dll | 10001.1.1.557 |
SolarWinds.Orion.Proxy.I18N.Strings.dll | 10001.1.1.557 |
SolarWinds.Orion.Security.dll | 10001.1.1.10224 |
SolarWinds.Orion.ServiceDirectory.BusinessLayer.dll | 10001.1.1.779 |
SolarWinds.Orion.ServiceDirectory.dll | 10001.1.1.894 |
SolarWinds.Orion.Swis.Client.dll | 10001.1.400.898 |
SolarWinds.Orion.Swis.Contract.dll | 10001.1.400.898 |
SolarWinds.Orion.Swis.PubSub.dll | 10001.1.400.898 |
SolarWinds.Orion.Swis.SchemaProvider.dll | 10001.1.400.898 |
SolarWinds.Orion.Topology.Calculation.dll | 2015.2.0.200 |
SolarWinds.Orion.Topology.Calculator.exe | 2017.3.5300.1794 |
SolarWinds.Orion.Topology.Common.dll | 2015.2.0.200 |
SolarWinds.Orion.Topology.Data.dll | 2015.2.0.200 |
SolarWinds.Orion.Topology.Framework.dll | 2015.2.0.200 |
SolarWinds.Orion.Web.Integration.Common.dll | 2017.3.5300.1794 |
SolarWinds.Orion.Web.Integration.dll | 2017.3.5300.1794 |
SolarWinds.OrionScheduler2.dll | 10001.1.1.10137 |
SolarWinds.Packaging.Contract.dll | 1.0.0.729 |
SolarWinds.Packaging.Core.dll | 1.0.0.729 |
SolarWinds.PollerChecker.Contract.dll | 2017.3.5300.1794 |
SolarWinds.PollerChecker.dll | 2017.3.5300.1794 |
SolarWinds.PollerChecker.Plugin.Core.dll | 2017.3.5300.1794 |
SolarWinds.PollerChecker.Plugin.PollerChecker.dll | 2017.3.5300.1794 |
SolarWinds.Reporting.dll | 2017.3.5300.1794 |
SolarWinds.Security.Cryptography.X509Certificates.dll | Unknown |
SolarWinds.Security.Cryptography.X509Certificates.x64.dll | Unknown |
SolarWinds.Serialization.dll | 1.0.67.0 |
SolarWinds.ServiceDirectory.Client.Contract.dll | 1.1.0.6 |
SolarWinds.ServiceDirectory.Client.dll | 1.1.0.6 |
SolarWinds.ServiceDirectory.Contract.dll | 1.1.0.6 |
SolarWinds.ServiceDirectory.dll | 1.1.0.6 |
SolarWinds.ServiceDirectory.LocalCache.dll | 1.1.0.6 |
Solarwinds.Settings.BusinessLayer.dll | 1.0.0.64 |
Solarwinds.Settings.dll | 1.0.0.65 |
SolarWinds.Shared.dll | 10001.1.1.158 |
SolarWinds.Shared.Strings.dll | 10001.1.1.158 |
SolarWinds.Syslog.dll | 2013.2.0.6 |
SolarWinds.Syslog.Strings.dll | 2013.2.0.6 |
SolarWinds.WebLauncher.exe | 2017.3.5300.1794 |
SolarwindsDiagnostics.exe | 2017.3.5300.1920 |
StopNetPerfMon.exe | 2017.3.5300.1794 |
SWAlertActions8.dll | 2017.03 |
SWAlertEngine8.dll | 2017.03 |
SWSubClass.dll | 2017.03 |
SWSysLogActions.dll | 2017.03 |
SWTrapActions.dll | 2017.03 |
SWTrapService.exe | 2017.3.5300.1794 |
SyslogService.exe | 2017.3.5300.1794 |
SyslogViewer.exe | 2017.03 |
System.IO.Abstractions.dll | 2.0.0.144 |
System.Reactive.Core.dll | 2.2.0.0 |
System.Reactive.Interfaces.dll | 2.2.0.0 |
System.Reactive.Linq.dll | 2.2.0.0 |
System.Reactive.PlatformServices.dll | 2.2.0.0 |
taskschd.dll | 6.0.6001.18000 (longhorn_rtm.080118-1840) |
tdbgpp8.dll | 8.0.20034.14 |
TDBWSnk6.dll | 5.00.0020 |
todgub8.dll | 8.0.20034.18 |
TrapViewer.exe | 2017.03 |
Vim25Service.dll | 0.0.0.0 |
Vim25Service.XmlSerializers.dll | 0.0.0.0 |
Is there a way to hide tabs in the client view for Web Help Desk?
Specifically I would like to hide the Messages and Profile tabs as I don't want clients accessing them.
Thanks in advance for any responses!
We've adopted Meraki to replace ASA 5505's in SOHO solutions, and I'm replacing 60 of them now.
But I find insufficient Solarwinds support for backing up MX65's, Z3's, etc. Nor do I find excellent snmp-v3 information about monitoring Meraki gear with NPM.
I've searched Thwack for "meraki" and reviewed lots of hopeful, optimistic entries, plenty of requests for SW to better manage or integrate with Meraki gear. But I've found no answers to my needs. I can only discover my gear with plain snmp-v2, and I can't back it up at all with NCM.
Nor do I see a way to pull Netflow info from Meraki for NTA to display.
Do you use Netflow on your Meraki gear and have it successfully showing up in NTA? If so, how?
Have you found a way to back up Meraki gear with NCM? If so, how?
Have you successfully implemented snmp-v3 between Meraki and NPM? If so, how?
Your stories, answers, solutions, workarounds, frustrations, and suggestions are requested!
We are trying to build a compliance rule to check for a "log" statement at the end of each permit statement of an access-list. The entries in the ACL are different for each device but all entries must have the "log" at the end.
For Example, this device should flag because one line is missing the "log" statement:
access-list 25 permit 192.168.207.48 log
access-list 25 permit 192.168.207.49 log
access-list 25 permit 192.168.207.47 log
access-list 25 permit 192.168.205.205 log
access-list 25 permit 192.168.205.206 log
access-list 25 permit 192.168.2.1
access-list 25 permit 192.168.206.170 log
access-list 25 permit 192.168.248.96 0.0.0.31 log
While this other device, using the same ACL 25 with different entries, shouldn't flag:
access-list 25 permit 192.168.205.205 log
access-list 25 permit 192.168.205.206 log
access-list 25 permit 192.168.182.169 log
access-list 25 permit 192.168.95.20 log
access-list 25 permit 192.168.248.96 0.0.0.31 log
Here's what I have now. I think i'm close but can't quite get there:
Looking at doing a weekly export of all configs to a group G-Doc repository. Is this possible? If so, how?
Hi
I have a problem with hardware health monitor.
My vcenter added to my NPM 11.5 and SAM 6.2.
One of my esxi server's HDD failed and I recive error and change the HDD .
But problem start after that. Error gone from server ilo and vcenter health monitor but in Solarwinds HDD sensor still failed.
Disable and enable the sensor from SAM was useless.
Even I remove and add specific server again.
There is no error log even in server ilo.
So tell me what should I do?
Hello People,
I have requirement to Monitor all the PDU's installed in our Datacenter through Orion : PVI (Power - Voltage, current, Ping etc )
We have Chattsworth PDU installed in our Datacenter - those are metered and IP and connected in daisy chain with one acting as primary
In our data center, each row of PDUs are serially connected and one is designated as the Primary which is connected to a network switch to provide web access
Questions :
Does Orion Support this if yes do we have OID adn MIB for those PDUs
Also if someone can share to start with this
Many thanks in advance
A coworker extracted a few thousand virtual machine hostnames from VMWare for me, and I'm using that list to seed Sonar Discovery in batches of 100 nodes at a time. The problem I am trying to solve is tracking with nodes were accessible via SNMP or WMI, and which ones were ICMP only. What I'd like to do is somehow feed the results to the master spreadsheet and update each node as Added(WMI/SNMP) or not added(ICMP) so that I can communicate my progress to my teammates by sharing the spreadsheet. Currently, I manually read the discovery results and update each node status, but that is pretty tedious.
Is there a better way to do this?
Hi All,
Just a quick clarification required on ESX/ESXi/Vcenter monitoring. Is SNMP must while configuring these types of devices in Solarwinds? OR just the credentials will do the job....
hi expert.
I have been asked by customer regarding what is the maximum concurrent connection supported by ncm to do batch upload to devices. and what is the best number for the setting.
kindly please help me..need to update asap to end user.
The SolarWinds Academy is excited to announce the official launch of the new and completely updated SolarWinds Certified Professional® program.
Based on the feedback from SCPs around the world, we focused on two key aspects of the program that needed attention: creating lasting value for SCPs and helping SCPs succeed.
We want to create lasting value.
We created the SCP program in 2009 because we knew our customers wanted to demonstrate that they have the skills needed to manage networks effectively using SolarWinds products. Unfortunately, as time passed, the program did not grow with our products. The SolarWinds certification became outdated, and did not hold enough value to be a competitive player on the global IT stage.
To create lasting value, we made two key changes:
We want IT professionals to feel pride and a sense of achievement at becoming an SCP.
We want our customers to succeed.
Our customers’ success drives everything we do. Because the world of IT is always growing and changing, continuing education is an integral part of being a successful IT pro. To encourage continued growth, we added several benefits that members can use to increase their knowledge.
New benefits include:
OPTION A
YEAR | BENEFITS | FEE | Expires |
Single exam option |
| $200 USD | 3 years |
OPTION B
YEAR | BENEFITS | FEE | Expires |
First Year |
| $200 USD | Your certification is active as long as you are a subscription** member and attend required events/training |
Subsequent Year(s) | Same benefits as year one, plus:
| $200 USD |
*Only includes exams that are part of the new SCP program.
**Your subscription does not auto-renew
SCP webcasts: You’ll have access to exclusive live SCP webcasts where you can interact with product managers, Head Geeks™, and other IT professionals to discuss the future of SolarWinds products. For our members who can’t participate in a live webcast, we’ll record all events and post videos only available to SCPs, along with the comments that you can view as often as you need.
SCP online advanced training: We’re offering advanced-level training for members who want to gain a deeper understanding of SolarWinds products. Our experienced SolarWinds Academy trainers are dedicated to providing the most up-to-date and comprehensive courses for SCP members. Join exclusive live WebEx® classes and interact with SolarWinds Academy trainers and other SCP members.
Invitations to live events: Our live events are not only an excellent way to learn more about SolarWinds products, but also provide opportunities to network with other SolarWinds Certified Professionals and SolarWinds team members. Collaborate, network, and get awesome swag all in one place.
You spoke. We listened.
Because we truly believe in the success of our customers through continued education, we don’t want personal finances to be a determining factor of whether a person participates in the new SCP program. Our SCP subscription plan will be available for purchase in the THWACK® store in the coming weeks. For 60,000 THWACK points, you will be able to purchase* a one-year SCP subscription. The more active you are on THWACK, the more points you earn. We will update this thread when the exam becomes available for purchase in the store.
*For select countries only - US, CA, UK, DE
Additionally, our THWACK MVPs, will receive one free SCP exam a year. Click here to learn more on how to achieve this status.
We hope that the new SolarWinds Certified Professional program brings you value and enhances your knowledge of SolarWinds products. If you have any questions, please review our FAQs, ask us on THWACK, or send an email to certification@solarwinds.com.
I have an issue with hardware health monitoring in my environment.
I have vCenter 6.0 and 3 clusters.
2 Clusters include IBM hosts and other one Include HP hosts.
In monitoring side I have NPM 12.01 SAM 6.3.0 VIM 7.0.0 WPM 2.2.1 and SRM 6.3.0.
I have also additional poller.
Vcenter and All ESXi servers poll through additional poller with SNMP and Vmware Polling.
Also I added vcenter to VMAN .
now problem is that Solarwinds dont show any Hardware Health info for this ESXi Servers
I installed OEM iso version of ESXi on each server.
Hardware health info for hosts shows successfully in vSphere webclient and also I check states in vCenter MOB. Every things is OK.
Also I checked "All Settings---> Manage pollers ---> Hardware Health Sensors" Scan Results is "Not a match".
Additional poller version also is the same with main solarwinds server.
I am so confused.
Any help could be great for my situation.
Thanks
Also I read this links before sending this post :
SAM Hardware Health Supports Lenovo ThinkServer
We're evaluating UDT for tracking the movement of IP phones on our network. I'm playing in my office with a couple switchports and Raspberry Pi's to simulate this. It seems to be very inconsistent in whether it works or not, and tends to be usually NOT working.
Trying to figure out what’s going on, there seems to be some inconsistencies. One thing that’s bugging me is something I’m seeing in the Port Details in UDT. I have 2 ports in my office that I’m using, there is no switch/hub hooked into them, so at the most I should be seeing a single MAC address on the port at any given time. However, UDT is reporting multiple MAC addresses on them. I have confirmed via the command line that at the time of this polling there was a single MAC address on the port. Furthermore, one could argue that if a port is “down” that there should be no “current” MAC-addresses on the port. Now, it might take a little time for the switch to age out the MAC address from its table, but no more than 5 minutes. But even when Orion is knowing that a port is down for quite a few polls, it’s still showing MAC(s) on the port. To me, both of these are telling me that UDT is not actually reflecting the current state of the port, which is bad.
This seems to be causing issues with the “Port History” shown here also. Of the 3 MACs on Gi4/0/10, only the one ending is 17:7D is current. But yet both switchports, the one that is UP and the one that is DOWN, are showing multiple MAC as being “CURRENT” in the “Port History”, not good.
esw-03-1498-253-1#sh mac address-table int g4/0/10
Mac Address Table
-------------------------------------------
Vlan Mac Address Type Ports
---- ----------- -------- -----
231 b827.eb79.177d STATIC Gi4/0/10
Total Mac Addresses for this criterion: 1
esw-03-1498-253-1#sh mac address-table int g2/0/5
Mac Address Table
-------------------------------------------
Vlan Mac Address Type Ports
---- ----------- -------- -----
esw-03-1498-253-1#
But as you can see, its showing this MAC as active on two different ports on the same switch. This should never happen, a mac address-table on a switch associates a given mac to a single port. But even though gi2/0/5 is down and Orion knows it is, it’s still registering the same mac on two different ports of the same switch. Not good. The port that is down should show no current MAC addresses.
I think this is what is causing issues with the MAC MOVE alert. I was going to write a custom report to show the MAC’s that had moved in the previous day, and while working in SWQL studio I saw the following. When I looked for the MAC I’m playing with, it shows as being “IsCurrent” on two different ports at the same time on the same switch. Once again, bad. You can also see from here that the operational status on one of the ports is “2” which is “DOWN”. A “DOWN” port shouldn’t have any active MAC’s for any extended period of time.
To me it looks as if the port goes from an UP to a DOWN state, that all MAC’s on that port should stay in the history, but not be current. If the port goes active again with the same MAC it had before it went down, you could remark it as active without adding another entry into the history. That I’d be ok with. But leaving so many active I think is confusing the mechanics of things like the MAC move report.
This seems to be a fundamental issue with UDT not reflecting the current status on a port, whether it be UP or DOWN.
Anyone else experiencing these issues? In our environment we have NPM 12.2 and UDT 3.3.0.
Hi
Can any one advice me how to add DDN storage in SRM for monitoring.
Hello my fellow thwack members,
My company has been running NPM, NCM, NTA, and UDT for the past several years. Recently we purchased licencing for SAM and I noticed "DPAIM" under licence details...
I'm now wondering if the DPAIM module's licencing falls under SAM or something?
Does the DPAIM module get installed by default when installing SAM?
I currently use SAM to monitor my Solarwinds SQL Server, doesn't that use Database Performance Analyzer ?
Any help understanding the difference in licensing for DPAIM and SAM would be much appreciated.
I've attached screenshots of the SAM and DPAIM modules.