Community
Command Central
MVP Program
Monthly Mission
Blogs
Groups
Events
Media Vault
Products
Observability
Network Management
Application Management
IT Security
IT Service Management
System Management
Database Management
Content Exchange
SolarWinds Platform
Server & Application Monitor
Database Performance Analyzer
Server Configuration Monitor
Network Performance Monitor
Network Configuration Manager
SQL Sentry
Web Help Desk
Free Tools & Trials
Store
Home
Products
Network Configuration Manager (NCM)
Cirrus Eval caused my Core Switch to CRASH!
mgreco
I started using the eval of this product, and was pleasntly surprised with the smooth install and time to start working with the product. I added necessary configruation information (SNMP and login information) and went to work adding devices.. 2 IOS based switches later, things seemed fine.. Then i added a CatOS (version 8.3.(2)) device.
Low and behold, the network started having issues. I thought it odd that this tool could perhaps have caused the issue, so downplayed that as a possibility. (turns out the device rebooted somehow)
I added a different CatOS device (another critical device!!), and all of a sudden that device rebooted!! I'm sitting here thinking, this eval is not going so good, and how is it going to pass muster with management.
I'm shocked that a tool marked for eval would cause such havoc on the network.. Has anyone experienced this issue?
Find more posts tagged with
Accepted answers
All comments
greg
mgreco,
I have not heard of anyone experiencing the CatOS devices rebooting simply by adding the devices to Cirrus...
Cirrus uses industry standard SNMP and ICMP to determine the device's status, and TELNET/SSH to run commands on the device. I don't know of any problems on CatOS which cause spurious reboot when receiving these types of packets... Anyone else?
It is possible to reboot devices using Cirrus, but that requires either executing a script, or setting up a scheduled job to execute a script. A reboot can be called from a script by using the ${REBOOT} macro.
Could you please call the support department at 918-307-8100, so that we can get some more information regarding the issue you are describing?
Thanks for trying the eval,
Greg
mgreco
Turns out, use of this Cirrus version (2.0) can trigger a know but rare SSHv2 bug in cisco CatOS version 8.3(2). Apparantly, this bug was fixed by cisco in 8.3(4).
see the following Cisco Bug ID..
www.cisco.com/.../onebug.pl
greg
Mgreco,
Thanks for finding the relevant info on this issue!
Greg
Quick Links
All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of