Comments
-
It would be great for the vendor to chime in and give stats on how many people this issue is affecting and how widespread the problem is. It sounds like the 2023.3 RC version has not corrected this issue. Do we have idea's on how many APE(s) / nodes there are before this becomes an issue? Is the workaround of restarting or…
-
Can anyone confirm whether this issue is still with the latest Hotfix 2023.2.1?
-
Does anyone have a Case number? I want to track that this is fixed in the next release before we upgrade. There should be an easier mechanism to track these issues for the community.
-
How do we remove the icon in question? The unexpected alteration in the user interface has caused discomfort among our clients. We do not have HCO and would run into security issues using platform connect. We would much rather not have this icon present.
-
The 2023.2 version's release notes indicate a considerable number of additional fixes beyond those that were documented in the 2023.1.1 release notes. Could you kindly advise if a 2023.1.2 version is currently under development and scheduled for release in the near future? Although we are eager to obtain the fixes that…
-
Thank you for this info! I found it difficult to find and your help is appreciated. With flexible licensing can you change the quantities as the environments change? For example, if we have 2 environments setup with HCO, nodes split evenly. Six months down the line one environment shrinks by half and the other doubles in…
-
Working again!
-
The is vital functionality for us. We need a workaround or a hotfix.
-
Thank you for the reply. I don't see an option for LA above 1000 nodes. Is there an unlimited node licence class? Syslog and traps don't use the agent for the network gear so I think we are good there, and we can spread out any windows nodes to make sure no more then 500 per APE.
-
Thank you for providing details on your process. I would like to see this as an option in the product itself as we also see events daily where the agent goes unresponsive. As your using open source tools I'll open a feature request to see if they can add this functionality to the suite. I'm eagerly following along as we…
-
Can you please share how you are using automation tools to do the SolarWinds service agent restart? What tools and how are you kicking it off. Are you using an alert to kick off a program?
-
In the Alerts tab you can Pause actions of all alerts.
-
You should only need the results from the Read-only string to send to support. We only setup our devices with a read only string to prevent changes via SNMP.
-
Yes, that is V2, and your Read-only community string is sarpub, your Read-write is privind
-
The version refers to your SNMP setup on that device. One way to check this is to match what you are using in Orion to the SNMPwalk. v2 is a community string v3 is a username and password. Edit the properties for that device in Orion and see how you are polling it under Polling Method. This example is for SNMP v2.
-
Are those release notes available? Are these different fixes then what will be brought in when HF3 is released for the core platform that the other modules use are released?
-
We are installing an Eval today and notice that 2019.2 HF 3 is going to be installed. Are there release notes on what this HF addresses? The Success Center is only referring to 2019.2 HF1.
-
There needs to be better viability into ongoing issues. FYI - Looks like HF 5 is due out on Aug 20th https://support.solarwinds.com/Success_Center/Orion_Platform/Orion_Documentation/Orion_Platform_2018-2_Hotfix_5
