Comments
-
See this thread:
-
Jp, can you please open a support ticket on your merging issue? There's no reason why the merge that you described shouldn't work properly. We definitely want to get this fixed. Just to make sure we're clear, you are using the scheduled Orion node import job in the Scheduled Jobs list:
-
I think this link on the Bandwidth Monitor describes its setup well: https://support.ipmonitor.com/helps/13a7520467994df6a4f3bad6b0a096f6.aspx
-
We looked at trying to resolve this in the release we're currently working on, but it was too close to feature complete. We'll look at this for another release. In the interim, you can try using this custom resource developed by one of our community members (Gob):
-
It appears the slowness is in waiting for the current command we just sent to be echoed. We're seeing the current command + command prompt together as one string so there's a long delay while we time out. You're running v4.0.1, correct? If so, please submit a support ticket and we'll look further into this one in the lab.
-
Thanks. Regional settings compability is on our roadmap.
-
When you installed the NCM integration module in Orion, you did not get prompted to run the Orion Configuration Wizard? If not, then yes, please do run that again. This is required to install the NCM integration module.
-
Please see Orion NPM doc: www.solarwinds.com/.../wwhelp.htm (Setting Account Limitations).
-
Can you post the session trace for the device? Enable session tracing by going to File > Settings > Session Tracing. Then, attempt to download and post the resulting trace found in <install dir>\SolarWindsConfiguration Management\Session-Trace directory.
-
That is a good assumption ;-)
-
This is top news. Just looking at the demo now, very happy, and looking forward to this, it's exactly the direction Cirrus needed to go. Top marks! Thanks, we appreciate the positive feedback. We realize we're not done yet and will continue to bring more and more functionality over time into the new website. Will this now…
-
They should get back to you with requests for more information, but you might export your current configuration (including monitor settings) at attach so they can more easily reproduce.
-
It looks like this feature request is in the wrong forum. Can you please post to this thread: Re: Tell us your "Unknown" devices!
-
dclick, I hear where you're coming from. I think Elisabeth just wanted to ensure that this evaluator got hooked up with one of our sales professionals to help this user with making an informed purchase decision. We do take commonly asked questions or tips/tricks and include them in our KB system (www.kiwisyslog.com/.../).
-
That makes sense. So, you're saying if a device hasn't responded to one or more of those protocols within the last X days/weeks/year, then delete them. I'm curious how often this occurs? Are there a lot of devices that age out in this manner or is this a once per year exercise?
-
This isn't possible yet, but it's coming in the next release.
-
Would you mind posting your Nortel Secure Router template to the content sharing zone? http://thwack.com/files/folders/cirrus_device_templates/default.aspx now i am trying on some nortel Access Node (AN) and Advanved Remote Node (ARN) the Cirrus console logon in the equipment but then stops all in the prompt Can you enable…
-
Have you tried the Cisco ASA template in the content sharing zone?
-
My question, if i move NCM away from the NPM poller server, but still have the integration module installed, can i still send all syslog to the main NPM, and NCM will pick up the relevant syslogs? No. The NCM integration module is a website-only integration with Orion NPM. It doesn't provide any "server" capabilities so it…
-
We currently do not expose the interface name as a variable in scripts, but this is absolutely on our roadmap. Today you can use the inventory report to pull a list of interface names for each node, export, and use that to generate your command scripts.
-
After further research into how SDEE works, I think we're all in agreement with jswan on this one. It's highly unlikely we'd ever undertake this kind of effort, especially given the limited number of requests for this capability.
-
For internal folks, we're already tracking this as #4170.
-
<Command Name="VirtualPrompt" Value="Enter switch number to connect to or <CR>:"/> this seems to die and I am thinking the < and the > are tossing it off. I know it must be as I just put the line: Ok, sounds like you're making some good progress. You'll need to change the virtual prompt value to the following to use > and…
-
If there are updates required out of band, we (or our community members) will post them to the Content Exchange When you say that NCM 5.5 is not detecting the ASA5520 correctly, can you clarify what you mean? Also, what is the system OID of your Cisco ASA listed in the device details view? The 5.5.1 Cisco ASA template…
-
Jeff, are you currently running 10.0 SP1? If not, perhaps the support rep was providing you the workaround if you didn't want to upgrade? Otherwise, I agree this warrants further investigation on our side. Let me know either way and we'll get to the bottom of this. Thanks, -Chris
-
When you view the nodes in the NCM desktop client, do they show up in the same way? If so, it may be that that a macro has been configured for the node name incorrectly.
-
We plan on addressing this in 5.1.
-
Are you sure it's TFTP traffic? I checked with dev and the response was: We use 8099 to talk back to ourselves, but that never leaves the box, should not need to be configured on the firewall.
-
Thank you very much for the post Jason. These use-cases are very helpful!
-
Ok, that's what I was trying to understand. When you say you have 4 servers running NPM, it's more likely then that you have 1 server running your primary NPM server and 3 servers running NPM additional pollers. This is all considered a single Orion NPM instance and can all be accessible through a single Orion website.…