Comments
-
Need to register the SQLDMO support.microsoft.com/.../248241 Find the solar winds sqldmo.dll file and register it. C:\Regsvr32 Sqldmo.dll
-
The ^ is telling it that the quit is the beginning of the line. In your config, there is either a tab or other character that is right before the "quit" so it is no longer the beginning of the line, but rather just part of the line. By removing the ^, it now ignores the whole line that contains the "quit"
-
Try this: Locate this line: Ignoring quit word line: ^[ \t\r\n\v\f]*quit[ \t\r\n\v\f]* and change it to this: Ignoring quit word line: [ \t\r\n\v\f]*quit[ \t\r\n\v\f]*
-
The fix you are referring to for the Orion Module Engine terminating unexpectedly is often due to the database making reference to the wrong poller. In some cases, the default engineid column in the nodes table get's set to -1. If you check the engineid from the engines table and set it correctly in the nodes table it will…
-
the only problem with this is that there is no way for me to know that there is a current download as of today. For example: In your gbserversk2.apac.local node, the last download was on 4/21/12 and the last download for lac1sk1.apacteleservices.com was 4/19 This would be considered the last downloaded config and there is…
-
You need to set the cli before the config download can happen. Here is a basic EX2200 template that worked for some. <Commands> <Command Name="Reset" Value="set cli screen-length 0"/> <Command Name="Reboot" Value="request system reboot${CRLF}yes"/> <Command Name="EnterConfigMode" Value="configure"/> <Command…
-
The following report fixed this issue. This report is an unsupported version and will break if modified via the NCM report utility. <Report Version="2.0" ReportType="Physical Entities" Schema="C:\Program Files (x86)\SolarWinds\Configuration Management\Schemas \Node_Details.Schema" Category="User Defined" Title="Serial…
-
Do you have maintenance? If so, you can create a case and send me the screenshots showing the issue so I can take a look and give you a call to help you figure it out.
-
Take a look at the Preinstaller.log file. Typically, it can be found here: (depends on your OS) C:\ProgramData\Solarwinds\Cirrus\Logging Otherwise, if you have a case open, what is your case number?
-
If you are having issues with the NCM database manager, you can always use the SQL Studio for sql to work with the database. When the database manager says "cannot connect" it is due to a timeout built in by microsoft. You have to right click and remove the server, then re-add it. This will require you know the database…
-
If your account that NCM uses to login to the devices does not have the rights to run the "terminal pager 0" command, the template will not work, because your environment will not let it. You could try to use tftp or scp as the download protocol so that you don't need the terminal command.
-
The name should be <name>-OID.configmgmt-commands eg. Cisco IOS-1.3.6.1.4.1.9.ConfigMgmt-Commands Within the file it should contain the same OID information eg. <Configuration-Management Device="Cisco Devices" SystemOID=" 1.3.6.1.4.1.9">
-
What is the ticket number you opened for this case?
-
When you say "Where is that done at?" do you mean where do you set the enable level? If you are using TACACs, logging in via User credentials, and only see the problem on a few devices, then you would set that within TACAC's for the failing devices. If you are logging in using Device Login, then right click on the device…
-
Hard to say on this one. Custom reports themselves are not supported, however if you open a case online we'd be happy to look at it and offer assistance if we can to see why it will not work as a job.
-
The first thing you want to do for ASA's is set the correct template manually. Right click on the ASA and edit the selected node. On the right side window scroll down to the Communication section. Next to the Device command template: change the auto determine to Cisco Adaptive Security Appliance. See if using the correct…
-
Once a node is removed it is removed from the nodes table and therefore not searchable. To track what nodes have been removed from the database you would have to check the events table. The eventtype for removed nodes is '8' so a query on events where eventype ='8' should suffice. Alternatively, the message field reads…
-
Actually, "no configs" would show up unless you had 2 configs that meet the criteria. One being the last downloaded and the other being the last known. It does not treat one config as both.
-
You are welcome, but I think you meant to say when you "DISABLED" it.
-
When you upgraded to 7.0, you integrated the databases. It should have asked you to run a synchronization that would then add the node back to NPM. At which point you can delete. Try to do manual synchronization, then delete the node from NPM. Go to your NPM website Click on the up right side where it reads Settings Click…
-
The trace indicates it is timing out before it can connect. Try the following troubleshooting steps: Right click on the device and edit selected node. In the right window locate the Actions button and click and select validate login. Does it validate? Also, try increaseing the telnet/ssh timout values located in the NCM…
-
User was working with multiple installations. NCM web integration can only view the nodes related to the NPM installation. He will need to install the web integration to each NPM installation to see the nodes related to that installation. issue resolved per case 266210
-
The error indicates you set the enable level to 0. Set it to "No Enable".
-
Start off by making sure the Path specified on the NCM server has the Network Services added to the security.
-
No, this does not permit for double IP addresses. Each IP address is a distinct node so NPM and NCM will not see it as the same node if they have different IP addresses.
-
Have you tried to delete the job and create a new job?
-
Ok, I responded to your other post. You need to first set the correct enable level. If the issue persist and you have maintenance, you can open a case on line and we can take a closer look at it for you.
-
Only a local admin account is supported, so regardless that a domain account has worked on this or any version, it has never been a supported account. Often, changing it to a local account has resolved such issues. More to the point, NCM jobs are basically setup as normal OS jobs in task scheduler. As a test, you can…
-
Typically, the only person that can clear the status is the person who started it. However, the work around for that is to go to the database directly and run the following query: delete from transferqueue Also ensure ,if possible, there are not any active transfers at the moment of query execution to avoid unexpected…
-
Ok, well if the device is sending NCM a password prompt, then NCM doesn't recognize it anymore and doesn't know how to respond. You could try to add precommand statement. <Command Name="PreCommand" Value="<enter your password here>" RegEx="Password:"/> This should send the value of the password when it sees the prompt…