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

Problems/Questions about Cirrus

I'm now running Cirrus VS 4, and before going to this version I was told it would solve some issues I'm having. The main issue is that if I have Node Monitoring running when I start Cirrus it takes for ever for me to do anything in Cirrus. If I dont have node monitoring running and I add a new node its not recognized correctly, it just shows as an ip address. Are these 2 problems ever going to be fixed? Is anyone else having this problem and just living with it?

Something unrelated to the Version and a problem that has been with Cirrus all along. I have several devices that are showing up as just Cisco, and not the correct device like Cisco 871, and 3560 is there a way that this can be fixed.

Find more posts tagged with

Accepted answers

kindbro

Thanks Chris, I will do that.

All comments

chris.lapoint

We're coming out with a service release very soon that should resolve the issues you described above. That is, "node monitoring causes slow console response" and "SysObject ID database is not synched with Orion".

I would recommend opening tickets with support to track your issues so we can ensure that we get you the service release as soon as it's out of testing and verify that it resolves your issues.

kindbro

Thanks Chris, I will do that.