Comments
-
I have been asking for a feature like this as well, CiscoWorks can do this....basically search for a criteria(missing or exists), and then take the search results and execute a job on them...which is usually what you need to do after you search configs!
-
<Configuration-Management Device="Cisco PIX" SystemOID=" 1.3.6.1.4.1.9.1.451"> <Commands> <Command Name="RESET" Value="no pager"/> <Command Name="Reboot" Value="reload noconfirm"/> <Command Name="EnterConfigMode" Value="config terminal"/> <Command Name="ExitConfigMode" Value="quit"/> <Command Name="Startup"…
-
if i use v3.5.1, and try to download the config from the 1 device, i get the connectivity message...if i revert to v3.0, it works fine...i have this same issue with another firewall now as well...so im going to stick to 3.0 until the next release.
-
Thanks for your help, still having issues though. The changeto in the enable command doesnt seem to work since it asks for a password, here is my current trace; -->StateChange: Connecting to server<-- Got HostFingerPrint: 9a:3b:3d:9e:50:0a:1a:ac:d5:8b:89:0b:ab:8d:9e:3a SWTelnet9 Crypto Information Begin Protocol = SSH1…
-
I have backed out my Software to version 3.0, as far as im concerned v3.5.1 is completely bugged. there are several problems with it, including this one. once i went back to 3.0 the problem went away.
-
Show running works fine, the problem is its not getting into the system context. the flow should go like this: login un/w FWSM\admin> enable FWSM\admin#changeto system FWSM# sho runnning
-
did you take the beta download offline? i can no longer access it. thanks.
-
has anyone solved this problem? i still have 1 device that all of the sudden started doing this via SSH.
-
nm, i see them attached in the beta invite.
-
haley, can you send me the current release notes for v4?
-
Hey Chris, I tried this and still not working, here is the trace: -->StateChange: Connecting to server<-- Got HostFingerPrint: 9a:3b:3d:9e:50:0a:1a:ac:d5:8b:89:0b:ab:8d:9e:3a SWTelnet9 Crypto Information Begin Protocol = SSH1 RemoteName = SSH-1.99-Cisco-1.25 SCcipher = 3des CSCipher = 3des Keys = SWTelnet9 Crypto…
-
that is a weird one, dont think i have seen that before....may want to call TAC.
-
Still not working, here is my session trace: -->StateChange: Connecting to server<-- -->StateChange: Connected to server - idle<-- Solarwinds.Net SWTelnet9 Version 9.0.27 Connected! --> ******************************************************************************* --> ProcessLogin State: 0 --> ACCESS IS RESTRICTED TO…
-
I have a ticket opened for the same issue, Solarwinds is aware of it...supposedly they are working on a fix and for now the above mentioned is the only workaround.
-
count me in.
-
I have the same issue with 3.5.1, i can also no longer discover new devices. I have opened a case and reverted back to 3.0 for now.
-
you may want to also try putting in items like this into your config comparison criteria, so they dont trigger a change detection.
-
so you are saying when you perform a show run you dont see the above VLAN configs? are you using TACACS? it sounds like there may be a rights issue.
-
i am also seeing this error now on a device as well, ssh and never had any problems until now.
-
Did you get this working? I am having trouble with your template.
-
this would be cool, since we have a similar situation on one of ours. post back if you get it to work.
-
I have also been able to use : ${CR}
-
4.01
-
are you going to publish the new features in the beta?
-
I would like to see searching of configs for keywords that are MISSING, and also to be able to load the results of a search into a new execution script.
-
yup, everything is as it should be. I reverted back to v3.0 and everything worked fine.
-
IF you are talking about rediscovering nodes, you can turn on node monitoring and it will rediscover nodes on an interval you choose.
-
I would also like to see this.
-
just installed 3.5.1, will report back if the issue has been fixed.
-
it seems this only fixed it when i run the jobs manually, when i schedule them they still crash