DX Spectrum is stable. However, now and then there are some issues, but overall it is good.

It's a very stable and mature tool. It's been around for a long time and has gone through all the changes the industry has gone through. It's rock-solid. I don't recall any bugs that prevented the use of the product.

It's a very stable product.

It is stable now. Over 20 years, we have seen a lot of crazy bugs, but in the last two or three years, there are no critical bugs there.

We did not encounter any issues with stability when the solution was properly scaled.

It's very stable.

Spectrum itself is stable. I think some of the other applications like the reporting solution tends to be a little bit of a problem for a manager. Whenever we apply patches and upgrades, it basically breaks reporting and we have to rebuild our reports. I have a whole bunch of automated reports that go out, and every time there's some type of an upgrade we have to rebuild those supports from scratch.

Out of all of the CA products that we use, I would say this is the most stable. We very rarely have issues with it, which is great because it is monitoring almost 10,000 devices for us.

It is a CA product. It is a mature product, but it does have issues. It does have issues that any product will have, but the nice thing is that CA does a pretty good job of addressing those issues.

I rate DX Spectrum's stability an eight point five out of ten. 

It's pretty stable for us. We have, not a highly available implementation of Spectrum, but we have an active standby situation, where we have an active SpectroSERVER and a standby SpectroSERVER and an active OneClick and a standby OneClick running all the time. So it works out pretty well that way.

I rate DX Spectrum's stability a ten out of ten. 

Stability is good, especially for large scale location redundant solutions with more than 80,000 devices in a single cluster.

In general, the location-redundancy with automatic failover is a myth, except if you are using Spectrum. If you setup spectrum in a redundant setup across 2 location (80 km in between), you can have a automatic fail over time within 10 seconds. This simplifies the maintenance of your setup a lot as well: any component can be switched off for maintenance purposes. The redundant instance takes over within 10 seconds.

SpectroSERVER and reporting databases can grow quickly. If you don't take care of trap storms, this can cause SpectroSERVER crashes and performance issues in the reporting.

From time to time we have issues with Spectrum. When we do, they are generally easy to recover from. I am very impressed with the stability of this product. I've been doing network management tools a long time and I know of what I speak.

Spectrum is quite stable.

It's been very stable and very easy to work with.

There was an issue with the REST API and a memory leak, but this was addressed very quickly and communicated via the CA Communities.

It's stable.

Occasionally, usually after an upgrade, we see a few issues but these are almost always cleared up quickly by opening a case with CA. The only “stability” issue would be very occasional problems with the “Archive Manager” component (manages the event DB) stopping and requiring restart. I would characterize stability issues with Spectrum as rare.

I haven't seen any problem. I'm a user, I'm not the administrator.

In my opinion, the stability is improving and getting better. Initially, we have had issues. Now, we are quite stable with the correct architecture.

I did not encounter any stability issues. Spectrum has built-in fault tolerance options that helps us build a high-availability setup.

It is stable. Our company has been using this for a long time. It does crash sometimes. We also encountered issues in regards to integration with some of the applications that are not using the latest version. So, there were issues.

It was quite stable. We had very few outages during the time I used it.

It is a very stable product. No software probably is without any downtime. There has been downtime here and there, but we have maintained well over 98% uptime with the product, and I have been using it for over 10 years. 

SpectroSERVER and reporting databases can grow quickly if you don't keep track of trap storms; this can cause SpectroSERVER to crash and performance issues with reporting.

I only encountered stability issues in very rare situations; mainly when we used our own extensions for private management modules.

I rate the tool’s stability a ten out of ten.

Stability has been good. We really have not had any issues.

Spectrum has been very stable.

It is a very stable solution. Once you launch it correctly, you barely have to manage it.

It’s been very stable for us. We don't experience many problems.

The stability is good. We have not issues in the two years that we have been using it. It is one of CA's more stable products.

It's pretty stable for a Windows product.

The stability of Spectrum is fine. We're just waiting on a new release to be put into play. We're excited about that because we're in 64-bit architecture, and the new release will be more stable and feature-rich. So, I'm really excited about delivering that to our program business unit’s infrastructure.

I rate the stability of the product an eight out of ten.

The stability isn't bad. There are Java issues but that could be because of our setup so I wouldn't blame the software. Although again, using Java is a little outdated. 

Stability could be improved. I find on a regular basis that those of us on-call tend to usually have to go in and restart or reboot a Spectrum server because the landscape's gone down. Then we have to worry about rebuilding databases whenever there's patching. This has gotten better with the latest releases, but we've still got to resolve that issue. For quite a few years, we'd have to go and sit there and wait for patching to occur, so we can go and repair all the databases after the fact because Spectrum couldn't shut down the database fast enough before the reboot.

I did not encounter any stability issues. Spectrum has built-in fault tolerance options that helps us build a high-availability setup.

DX Spectrum is stable. 

The solution is stable. 

DX Spectrum is a very good product. It's stable. We have not faced a lot of issues with it, so most of the time, customers are very happy with this tool. They're happy with its stability.

This solution is stable. 

This product is very stable.

It has been pretty stable. We have had no problems with Spectrum. 

The stability is very good - the best we've seen in the market.

Stability is good. The tool is a complicated tool. It's got a lot of pieces to it, databases, and you have to treat it well. You can't just turn it off randomly. There are pieces to turning it off, methods. As long as you know that then it is stable. 

We rarely have any issues with it. You have to make sure you follow the process correctly to shut it down, bring it up.

I don't have a lot to compare it to but I wouldn't say it's overly delicate. 

We haven't really had any stability issues with it, now that they've actually did some more upgrades. The biggest problem we had with it at the beginning was just the Java console. You had to have an older version of Java and then you had to go in and actually set the library up in the Java for another one. You had to make a lot of changes and a lot of people didn't want to go through that. That is the reason why I really like the web console on it now because you can get away with not having to install the Java console. If you have to add three more steps to a process, they just don't want to use it.

This is a stable solution and we have had no issues.

It's up most of the time. It's good. At first there were a couple snags here and there, but lately, it's been great.

One issue, after two weeks, we had to pass it up, escalate it, suddenly, and the next person went and solved it. Most of the time it's been solved or we've talked to engineers. Most of the time it's been good. No one's perfect.

There were problems with it going down, or generating extra tickets. But mostly, that got worked out after a little while, with tech support and us going back and forth getting solutions to the problems. It's been great recently.

What has surprised me most about CA has been the inner knowledge of some of their techs. I had no idea what was going on and they were like, "Hey, we got it."

It is very stable. It rarely fails and you can have a high availability implementation.

So far I've had no issues with stability. I've used it for about two years. Like any other software, it has a few hiccups here and there, but for the most part, it runs really efficiently.

I have not encountered any stability issues.

Not really on the CA site itself. We may have put under-powered servers running the application or things like that and those are some issues that we're working on internally to actually make it supported by CA. A lot of it really has to do with how much time you invest in setting it up and having the right hardware.

It seems fairly stable. We have had some issues with the spec server and the high availability replication of data. It fails over well, but it does not come back very well. We get duplicated events. 

No

We had some stability issues at the first, but CA resources in Argentina assisted us in to solving these problems. They also helped to fine tune our configuration to support the solution. In the early stages, we implemented a simple configuration of Spectrum, so sometimes we faced up-time problems. But that was due, in part, to the design we implemented. So, now we have implemented a more robust design with more servers and more robust databases. The solution is now stable enough to support the challenges we want to monitor.

It is very stable.

Stability has been great once you get it up and running. I've had issues getting new installs to work, but once it's finally going and all set up to go, it's been fantastic.

Scheduled discoveries with modelling of large numbers of multi-element devices like switches, MUX, SAN, IP-DSLAM used to freeze up the SpectroServer in r10, although such issues were not faced in r10.1.

I have not encountered any stability issues so far.

A device can't be 100% stable and robust. However, CA Spectrum is one of the most stable systems to handle at medium to high-level operations.

This solution is extremely stable, and it has proven this across years of use.

The tool is very stable.

I haven't had many stability issues other than during upgrade and maintenance windows.

In the beginning very much so, we are now at a point where it’s pretty stable.

No issues encountered.

The solution's stability needs improvement.

There are issues with any product, but for issues related to DX Spectrum, we receive upgrades. It can take some time, and occasionally we do not achieve the SLA times, but at the end of the day, we are getting our upgrades to the critical issues.

We do plan on continuing to use this product in the future.

Stability is very good.

I did not encounter stability issues. Even when the client disconnected because of a network problem, there was a change of state that would allow me to do some troubleshooting.

If database size is large and any corruption occurs, it takes a considerably large time to fix the issue.

Spectrum is a very stable product. It is a mature product, with a long life time in CA’s portfolio, and even before.

When we have a high capacity of traffic, we have problems with the stability of the system. This could be improved on in the future.

There were no stability issues.

At first, Spectrum was really difficult to configure properly. Today we are in a mature stage and the stability is really good. I think that the last version was more stable.

I’m a CA beta tester and found all issues that need to be solved in this program. I have no stability issues in my production environment.

v6.6 had few hiccups, but in general it is a very mature product. It's been around since 1991 when it was owned by Cabletron.

Only if the server that hosts the application is restarted without bringing down Spectrum. If this occurs it corrupts the database and has to be restored from the backup.

Sometimes a restart of the Tomcat Daemon was required, and sometimes the archive manager ran out of resources.

In terms of stability, it depends on the environment. Sometimes, the application does not function well because of the type of security and policies that are in place. Certain policies will block the application, making it unstable. We learned this after some of our customers complained and we investigated to determine why.

When we come across a situation like this we start working with their security department to address the issues, and then everything will start working well.

Overall, I think that it's a really stable product.

We lost our database at the end of 2016, and we spent weeks trying to restore it.

No issues with stability.

This solution is stable. We have not experienced any outages.

No, I don't think so. Every unstable state has been caused by an incorrect configuration, by overloading, or by hardware failure.

We've had no issues with stability.

It is very stable. We have not had any major issues in over 10 years.

It’s very, very stable which is the core benefit, and it’s also very easy to maintain. It doesn’t need much maintenance once it's set up. The strongest point of the product is it's stability.

Last year they didn't do a lot of development, and when they did it, it wasn’t secure enough. Each version took a long time to be stable, but it's gotten much better. Now it's totally stable, but 9 wasn't stable. 9.4.0 wasn’t stable, but 9.4.1 is. Overall, version 9 has been great.

I have never seen an outage of the tool.

Just minor but CA provided support to resolve the issues.

It's the most reliable product I have used.

No issues encountered.

No issues encountered.

I did not encounter any issues with stability.

We have not had any issues with stability.

We haven't had issues with stability.

There have been few issues with stability and overall it's very stable and effective.

There are a very few occasions when the system "barfs" and it looks like your infrastructure has gone dark, but it bounces back quickly (the system).

Latency in access at times.

We've had stability issues with the database and clients not working.

The most stable version I've worked with was the 8.1 and the 9.1.3 running on Windows Server 2003. Every versions running on Windows Server 2008 (R2) that I've worked after that (versions 9.2, 9.3 and 9.4) have had some issues either with OneClick/Spectro Server communication (hanged alarms for instance) or with global loss of SNMP communication with network devices, or DDMdb increasing indefinitely or with some unexplainable SSDB crashes. I haven't worked yet with version 9.10 but I am pretty sure that the 64-bit architecture was a huge improvement for the platform performance.

It is a very stable tool, even in distributed environments.

Yes, IM was very shaky and it seemed like CA were throwing hotfixes at us to fend us off until the next release.