DX Spectrum Reviews

What I like about the latest that they came out with is that 10.2 looks like it's going to be better, and they added a web console. I like the HTML5 fact of it, because it's a lot easier for me to get to my admins and other elements like that so they can look at their own stuff without having to sift through a bunch of stuff. I really like the web console addition, and from what I see from the 10.2, the whole thing is going to be HTML5. I really think that that's going to be real beneficial as far as me getting people convinced to use it and to actually look at it, instead of coming to me all the time for help.

It helped, basically, because we are working on root cause analysis. If we were to have outages, we really didn't know what the problem was, we just knew we had a server down. With Spectrum, we can do a root cause analysis by building topologies and we can actually tell you what port went bad on what device. Instead of just knowing that the device went down, we can know why it went down and exactly what happened.

If 10.2 goes completely to HTML5, I think that's going to be awesome. Just give everybody a website and tell them to log in and it'll be single-sign-on login, too, so they don't even have to remember another password. There is value in that alone, just trying to get people to log in and use it themselves, see it, and monitor it. They can monitor their own stuff and if something is wrong, I can do the tweaking, but at least they could see what's going on. I don't have to sit there and look at a dashboard and call everybody up and say, "Hey, your server's got an alert" because they don't want to mess with the Java console. They don't want to install whatever they have to, in order to do it themselves. I don't know, I call it laziness, but they're busy too. If it could fix it itself, that would be great! I think the way they're headed now with the roadmap and the visions that I saw. I really think that any improvements that they're going to make will be made in this next release. Basically, what I'm seeing right now, I think the improvements are happening..

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.

I have used technical support and they are very good. I've never had a problem. Usually I'll open up a case and I'll hear something back from them the same day. They're very knowledgeable with their products and very helpful, too. If I just don't have time to research something and I need it fixed, I just tell them "I need this fixed" and I never have an issue. They take care of it. They'll even connect remotely and do it themselves sometimes.

Be patient. In its current state, I would have a representative from whoever your partner is help you with it. From what I can see, when we implemented UI, it took 2 weeks of on-site representation from our partner to help get it up and running. I think it's something that it would be less painful if you did have somebody that knew what they were doing, one of your partners or something, come and help you install it and get it installed. Then after that, start running with it. Do not do it by yourself.

I choose a vendor based on their knowledge of the product. I need them to be able to tell me what I need to know and where I can go to get information. Don't try to sell me something and then tell me you don't know how to use it. I've had that happen with some stuff. For example, by saying something like, "I'm new at this". I need the knowledge. That's what I want from you to help me to succeed, because we pay good money for this stuff. We have MSOs and everything we pay for yearly, and I really do use it. I don't have time to sit there and always research something and read something, so if I call you with an issue, I really hope you know what I'm talking about and you can help me fix it.

We have been using this solution to supervise all of the network's components, such as our Cisco switches, UPS units, the firewall, DNS, and all of the things that have links with the network.

Good vision of devices problems 

The most valuable feature is the auto-discovery, which is nice because you don't have to do anything to add a new component. It will just supervise the links.

This solution is too complicated to use for us, especially if you have many components. It's too big for us, which is one of the reasons that we will no longer be using it.

It’s Cloud be difficult to upgrade from one version to the next.

We have been using CA Spectrum for five or six years and we are discontinuing its use in two or three months from now.

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

We have had no trouble with scalability.

We are moving from CA Spectrum because it is not a solution for us. We are moving to an open-source solution that is less expensive.

The initial setup and maintenance of Spectrum are complex. It is also difficult to upgrade to the more recent version. 

The product, support, and maintenance are all expensive, which is another reason that we are switching to another solution.

This is a good solution and I would recommend it for a big company. However, for a small business like ours, we need something that is less complex and easier to use.

I would rate this solution a six out of ten.

Monitoring. We set it up so that other people can watch everything and let us know if something goes down, or processing needs to be restarted. Then, sometimes, it just does that on its own. Air conditioner overheating. Stuff like that.

For the most part it has been good. There were snags in the beginning, learning curves, and the like, but it's relatively easy.

The monitoring just comes to us: "Oh, there's something wrong with that machine." It tells us. There are some 50,000 machines or so, all doing different things. And if they go down we hear about it.

It's improved things because we know when something's down and we know when something needs to be taken care of and when not.

The fact that I don't have to sit and watch things. They get monitored, and then I hear about them and take care of them as needed.

If they could interact with the MIBs of vendors better, and have a lot more pre-loaded ones, that would be amazing for us right now.

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's great. You can just keep adding stuff.

I would say it's a lot like other tech support. Some of it is great, and some of it is unreasonable. The ones that know their stuff, know their stuff. And the ones that are learning, are learning.

A couple other solutions. It cancelled some of those out. 

We switched because it was a bigger thing. We swapped so we could have support for just one monolithic thing, as opposed to a lot of little things. 

It just had more support, we could call somebody. It was very complex business software. We probably still don't use 40% of the solution at this point.

I would say mixed bag.

We wanted to make it so it was automated with a text file, so we didn't have to watch the little bar the whole time and answer those questions. We wanted all the configuration in one little file. So we had to figure out where that was and how they do that. Once that got done, then automation of getting it deployed to new environments, if we need to, is very fast. We just change a line or two in the text file and say, "Do this," and walk away. It's great.

My most important criteria when selecting a vendor are

• knowledgeable tech support
• reasonable forums
• documentation.

I give it an eight out of 10 because it's not perfect, but it's better than a lot of what's out there. There is still a lot of work you need to do on it. Even though it's a vendor product there is still a lot of support you have to have to get certain things. 

Again, we have a very diverse environment; Cisco stuff, air conditioners. To get all that to work to it's full potential with this product, monitoring-wise, is work. So if there was more interconnectivity already in it that would help. For instance, we had devices that were added six months ago that weren't operating to their full potential. Then we would realize, "Oh, this one needs to be done." So we have to run these end processes. Again, the are a lot of devices. Not all of them are doing this, but enough that we have to sift through them, manually, and get this one working and that one working. So that's why it's not a 10.

In terms of advice, I would tell people to load all the MIBs before you add the devices. Literally.

It has many great features, but in most of the companies that I have done consulting for, they rarely use them as it requires an advanced level of knowledge of the tool.

Event Configuration: A tool in its simplest form creates business logic around events. For example, generate an alarm if Event A occurs and if Event B doesn’t occur within 30 seconds. In its hardest form, you can create a custom state machine for very hard business logic.

Event Correlation: Spectrum has out-of-the-box correlation, but with this tool, you can create custom ones. You can make some alarms hide inside another alarm as a symptom, get root cause analysis, and avoid unnecessary notifications/alarms on the screen.

Topology view: The topology diagrams on CA Spectrum look very nice and they are very useful. We stopped using them because with more than10K devices, the administration was just too painful.

Dynamic models: Integration with the CA Spectrum is awesome. Sending traps with the third-party tools and using the SBG to receive them requires a learning curve. However, once you get it, it is very simple. Unlike another tool, you don’t need to know what the third-party tool is monitoring. In other words, if it sends some data, it will be dynamically created in CA Spectrum.

Reduces the false positives, by creating our own business logic with the Event Configuration.

Allows us to have a single console/notification point, with the alarms of all the tools that we use for monitoring.

It’s like having a Ferrari, without a professional driver. Most companies don’t use all the good features. The out-of-the-box features are just too poor: (Ping, CPU, Disk and Memory, Process, and File Systems). CA Spectrum is an infrastructure monitoring tool, that comes with a few easy to configure metrics, such as Ping, CPU, Disk & Memory, Process and File Systems. However, these metrics are really basic, actually we can do better with Nagios or any other open source tools in the market. In my experience, most big companies, that have CA Spectrum only use it for monitoring these basic metrics, i.e., where the real benefit is not there. If you only want it for this purpose, then there are better and cheaper options available.

It’s mostly for SNMP.

It doesn’t give you performance metrics: You need CA eHealth for this.

Some of the benefits of this solution (also mentioned above) are:

Event Configuration: It can easily (for an expert) create any business logic such as it can alert first, if you receive 2 events from Type A. If you already alert this kind of alarm and it happens again, then do it only, once every hour.

Event Correlation and Root Cause Analysis.

Service configuration (model a service).

Southbound Gateway integration – It can integrate with any other solution and dynamically, create models on CA Spectrum.

Alarms (impact, root cause, symptoms, etc.)

Watches – It can create custom metrics, besides the basic ones that I have mentioned before.

InfoView – It can create custom reports.

Topology view – This one is really difficult and time consuming, but awesome, if you can do it right.

Most companies spend money on the license, but they don’t have a good administrator, to make use of all the good features. So they end up with a really expensive tool, that does only the basic things, which any tool in the market could do probably better. But, the good features of CA Spectrum, only a few monitoring tools can actually do.

I have been using this solution since 2011. I got the CA Spectrum Professional Certificate in 2011.

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

Scalability and performance are great. We use both Nagios and CA Spectrum. We can say that Nagios needs around four times more servers than CA Spectrum needs.

I can’t really tell in regards to the technical support. It depends on the guy that answers the phone (Latin America). They have a really excellent technical guy who helped us a few times, but most of the times, the guy that answered the phone knew less than we did.

It was the first solution that we used when I started working. Right now, we are trying Naemon (Nagios). Here is my comparison:

Raw monitoring:

Naemon has a lot more flexibility, i.e., you can script and monitor anything with it, giving you more options than CA Spectrum.

Performance:

CA Spectrum is a lot better. The way they have for consulting SNMP in bulk is great, thus reducing the load a lot. It has around four times more performance with CA Spectrum.

Administration:

CA Spectrum offers you templates, Discovery tools, menus, etc.

In Nagios, we had to develop our own administration tools in order to discover and maintain over 10K devices. This needs a high understanding of the solution.

Business logics:

Here, it is a big win for CA Spectrum. With the events, you can make any of them interact with each other, even with different devices. I can’t think of any business logic that I wouldn’t be able to implement. (I am not saying it is easy, but with a lot of thinking, most of them could be done).

In Nagios, each service runs as an individual check.

The setup is complex for a big environment such as primary servers, slave servers, high availability, and fault tolerance.

If you have a small environment, it is very straightforward. You have the SpectroSERVER, OneClick, and database on the same server, although the recommendation is to split them.

However, the out-of-the box features are very poor for the price, since you are paying per device. You need to use the other features to make it worth it.

It’s a great tool, but an expensive one. Learn how to use it properly.

Try to learn, at least, the following:

Event Configuration

Device Certification

Watches

Alarm Notification Manager

Services

SLA

Spectrum is the total alarm management utility. All event alarms are displayed in one place. We use it as a complete infrastructure management tool. All our third-party tools report into Spectrum. That's probably the most valuable part of this software that we use.

It consolidates all of the traps, alarms, and issues that arise from any device or network equipment, to a central location. This makes it really easy to find problems that arise, narrow down their source, and then escalate to the right people to fix them.

Everything being centrally located in one infrastructure management tool allows anyone anywhere, between the IT help desk, to Windows teams, Unix teams, or the network team to see exactly what devices are causing the issue, as well as the severity of those issues. They can then prioritize and work on those issues that need to be worked first, allowing them to manage their time in terms of what they're working on.

Integration with third-party vendors could be improved by adding more trap solutions for third-party devices. These are now supported somewhat and I know that they're working on it, but people have a wide variety of different devices, servers, and equipment. It'd be nice to see all of that included into the software.

I think it still has room for improvement as far as the application, but support could also be improved. Third-party integration and other features have been requested over the years. I feel their support staff could work on these a little bit more, but as far as the application goes, I'd give it an 8/10.

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.

Companies from our size to larger organizations use Spectrum, so the scalability is there. I have never seen an issue with performance or the need to add more servers or scale to a larger environment. That hasn't been an issue.

The technical support is not bad, but I find that I generally resolve the issues before technical support can. Generally, I don't use their support too often. It's not about their support. The higher up you go in their support structure, I feel that they're very confident. But, I'm just a self-thinker and I'll figure the issue out before they do most of the time.

When I started, we were already using the solution and, as far as I know, it has been with us for 5-10 years. We've used it for quite some time.

When looking for a vendor, the application is most important. That's what stays with you the longest period of time. Again, you may not have to call support and you may not have to deal with sales very often, but the application is the one thing that you're constantly involved with.

I was involved in reconfiguring the environment. I guess you could call it an initial setup. Everything was pretty straightforward. It's easy to install and easy to setup. I haven't had any management issues or issues from configuration.

For what you're getting with the product, I don't think price is a downside. I don't know if it would be possible in the future to have a lite version, but something that smaller companies could work with as well would be a benefit to them. At current prices, for small businesses it's a downside. For bigger companies, I don't think it's too much of an issue, because otherwise they wouldn't use the product.

There weren't really other options. I've looked at other vendors. This is what my company went with, what we've used for a while, and we know it works. So, don't fix what's not broken, basically.

I would recommend the product to anyone looking for an infrastructure management application. I do know that for smaller companies the cost seems a little high, so it may not be for everyone. But, if you're looking for a total package that’s easy to get started and get it working, and something reliable and scalable, I would recommend the product.

With CA Spectrum Southbound Gateway, it is possible to receive alarm data and turn it into events. With events, it is possible to correlate ICs, other events and shape any function to its will.

The southbound gateway can receive data from third party sources, other monitoring products, like SCOM from Microsoft, using the Southbound Gateway you can centralize all Management in one view, you receive SNMP data from other tools and turns in events, events in CA Spectrum turns in to Alarms, QOS or reports.

With CA Spectrum, we are now able to monitor more proactively network assets, reduce the total downtime of these and prevent money from being lost for device stoppages. The tool also gave us an event integrator for all other solutions, including non-CA solutions, forming a consolidated view of all information sent. From customized polices, we can standardize device nomenclature, facilitating the opening of external tickets and improve tracking them.

The EventDisp Logic (Code) is too complex.

I have used it for one year.

I have not encountered any deployment issues.

I have not encountered any stability issues.

I have not encountered any scalability issues.

Customer service is excellent.

Technical support is an expert team.

I previously used Nagios and Zabbix, but CA Spectrum is more efficient.

Initial setup is easy, but configuration properties and EventDisp is quite complex.

A vendor team implemented it, but I participated.

CA Spectrum have a good model of licensing; the prices are based on types of models. If you understand the event processing code (Southbound Gateway), you will reduce the licensing price by more than 50%.

CA Spectrum is a powerful product for monitoring network ICs; if you master the EventDisp logic and the Southbound Gateway Toolkit everything, becomes easier.

It is important to remember that with the size of product, some caution should be taken.

The network monitoring features are the product’s most valuable, due to the lack of these capabilities in any other monitoring tool. No other application monitors networks as well as Spectrum.

Free tools are available to do what its other features do, such as server monitoring (CPU/memory/disk).

We are not using the latest version of the tool yet, but as far as I know, I think an improving reporting of data would be a good idea. The report area is very poor and we cannot work properly with additional information and the custom reports. We just use the default report for information that we have inside the database for these reports.

I've been working with this tool for eight years.

To be honest, Spectrum is one of the most stable and less problematic solutions that we work with. It’s easy to scale and to deploy. The only time we’ve had problems with it was with some upgrading processes. It is not so intuitive and you have to make sure everything is correct.

The CA support team is really capable and efficient when it comes to Spectrum. Most of the time they help us surprisingly fast and correctly.

I’ve worked with free tools such as Zabbix / Nagios. Right now, we only work with CA products and, as I’ve written, Spectrum is the way to go when you need networking monitoring.

Setting up general monitoring is straightforward. However, if you need something different than the standard setup, some customizations need to be done. Thus, it becomes more complex as a whole.

We have an ongoing vendor support team and we have an in-house one. For implementation advice, I would say to always plan your monitoring according to what you really need to monitor on your environment. Most of the problems we find today are related to operation process issues and not the tool at all. People have to know what they want before implementing the solution.

As I’ve written, not only for Spectrum, but for any monitoring tool, you need to know what is critical in your environment and think how exactly you should monitor and treat it. If you have done that, everything will work just fine.

The most valuable feature for us is that we can model a large variety of devices and receive SNMP traps from them.

It allows us to respond to network events, and we have a surveillance department that monitors all these inbound reports and we can get people dispatched right away.

A lot of things are internal development, like we'll have a network alert and we've got it configured so that it can open a trouble ticket and service management system. You know, a lot of features like that are the ones that we can develop internally without necessarily having it added to the software release, but it would be nice to have it added nevertheless.

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.

I haven't personally called them.

I didn't do the initial setup as far as installing the application. I've done a lot of tweaking of views of what the user should see and things like that and that's not difficult.

It's really tough to say because it really does have a lot to do with how much time you put into it. If we had a crew that just completely dialed in everything and set it up, had the right hardware, it's kind of a totally different question than if, internally, you developed it on unsupported hardware, didn't spend much time setting it up.

We've had a few previous competitors over the years that I've worked with the company. Spectrum can do SNMP inquiries and alert you that a device is totally unreachable. With some of our previous platforms it was a one way process.

Go for it. Try the best you can to start out fully within specifications and that kind of thing. We're going back and fixing all that now, which we might not have had to.