The initial setup was fairly straightforward. The system works off a master cluster, so it's easy to set up and easy to understand.

Our deployment took about a year. That was 15 years ago, but other implementations have taken a lot less time, moving forward. Our network was very complex so a lot of device certifications had to be done with SevOne, early on, to get what we needed out of it. But within the first couple months it was usable. It just took us a year to finally get us to where we wanted to be, with all the customizations.

Our initial implementation strategy was that we deployed SevOne and left the old system up and running at the same time. That way, we had a failover capability to go back to the old system, if needed.

We have hundreds of people in our company who work with SevOne. We have the NOCs that are monitoring the health of the network. We have the end-users that are monitoring their pieces, whether that would be an application server or a range of business. And then we have our commercial customers that are getting the utilization and health metrics of the services that we're providing to them. We also have salespeople who are monitoring it to make sure that their customers don't need to upgrade.

The initial setup was straightforward. 

We did a piecemeal deployment. The first pilot deployment was three months, but that was on physical appliances, so it was pretty simple.

The physical appliances were easy to implement. We installed it, migrating part of our estate and pulling from the incumbent system. We imported it using CSV, which allowed it to do a dual pull. Once it was dual pulled, we had to ratify the data that was collected by SevOne. This ensured that it was just as comprehensive as the incumbent system.

SevOne comes with multiple out-of-the-box reports. It is difficult when it is a migration. If it was a Greenfield implementation, then it would be easy since all our teams wouldn't have extraction techniques from SevOne, but we do. Our capacity plan team uses it a lot. It is a huge tool for them, but they don't really use the report techniques within SevOne, they just extract data. So, they extract report data and put it into a process that already existed. We had to put a piece of middleware in there to ease that process. All our customers will not change their process for dealing with performance data. So if you change the performance tool, then you have to do something about the bit in the middle. That has been one of the biggest bugs for us.

We already had teams who used performance data. They were used to the look and feel of it in a certain way. We had to accommodate that when we migrated to SevOne, and it is a great tool that is simple to use. However, if you want to change reports quickly, then it is good, but those teams have existing processes where they examine data and look at it, then we have to replicate that. For example, for the event-based stuff, we use Netcool, which is a big event-based IBM product. We had to go through a lengthy process to make sure that the events sent from SevOne matched the current rule files, so when they are plunked in front of the network management center, they look the same as they always have.

I don't know how long the initial deployment took, but I just recently added two extra nodes, and I am setting them up right now. Because we have the VMs, setting up is pretty easy. It is just a matter of the firewall rules and how we monitor only the objects that we want to monitor.

Our license is based on the number of object accounts and this is a challenge for us because if we enable every interface or every object on the device, it will exceed our license limit. Initially, we had trouble with how we can limit the number of licenses, and also how we can monitor only the objects that we need to monitor. Ultimately, it means that our object rules are a little bit complicated.

I wasn't involved in the initial setup. Before I came onboard, SevOne was running on a lot of physical devices. But I was involved in doing the upgrades and restructuring it to be more virtualized, so that could expand the cluster and the services. Being able to go virtual, drove the ability to scale, based on the demands of the business, fairly quickly.

The initial setup was very straightforward. It was really more of an issue just to get the money. And then once we had the money, it was very straightforward to roll it out.

We were driven by two migrations off of legacy components. It took us less than six months to get off the first system we were exiting, and then we spent another six months getting off the subsequent system. So it was probably about a year before we got off two of our original legacy performance management tools. And most of that was really around getting the data feeds sorted out, ensuring all the devices that need to be managed were part of automatic feeds into SevOne. SevOne itself is straightforward because it's an actual appliance base and it does not require much effort required to band it up.

Our implementation strategy was to replace like for like before exploiting any extra features of SevOne. We were collecting team metrics of 20,000 boxes. Then the replacement had to do the same as a starting point in order for us to exit the old system. So it was pretty much like for like, in terms of the implementation. And we did have a mix of PaaS and VM boxes as well. So we do have a mix within our environment for the collectors.

The initial setup is straightforward. If you know what you want, you can just go through the list, and it basically involves ticking boxes or radio buttons to turn on the features you want or turn off the ones that you don't.

I was not part of the initial setup because it wasn't on my network. What happened was we bought SevOne when our network operations team was part of IT. Sometime after that point, we were reorged into the network part of the organization and came under a new director who ran several other operations teams. It was that exposure to SevOne, through our team, to this director, that allowed him to see the value of it immediately. After that, he was pretty quick to say, "How do I get this to my other networks?"

After that, they stood up their own instance and put it into their critical elements. Since that point, they put in the rest of their elements and it's continuing to expand. I don't think they're going to stop there. I think they're bringing in other networks within the organization and the deployment continues.

Importantly, if you don't know what you want then SevOne is going to be there to help you get it to where you want it. They've been excellent. You can call the help desk, the support center, or you can call your customer support person, and they will find a way either to get you the data or to get you in touch with someone who can help you, or they'll call you back and do it themselves.

I don't know how long the initial deployment took, but our second deployment took about two weeks. It was completed by one or two people on our side. They set up a VM, installed the application on it, imported the data, and started configuring it. In total, fewer than five people are enough for deployment.

The maintenance requirements are pretty low. We have to do upgrades, but it doesn't take anyone as much as a day to complete them. It's not very labor-intensive in terms of support and over the past two years, we've needed to engage support only two or three times to assist with upgrades. Overall, it is not a product with heavy manual maintenance.

The initial setup is a little bit complex and you have to first create the main database. After you create the database, make sure you start collecting. Then you have multiple collectors that start collecting the information and send it to the database. They are really technical and it's Linux based.

The setup takes about one or two days.

Usually, when you do an upgrade it takes eight hours.

The initial setup of SevOne is very straightforward, due to the architecture of the platform.

We have different installations of SevOne and they do different things. The quickest deployment took about a month, including planning and securing internal virtual environments and licensing. But with respect to SevOne itself, the turnaround for deployment is about two weeks.

Our implementation strategy is to work with the support staff and the SevOne developers to run with it. All the assets, meaning the virtual environment, are secured internally and all the firewall ports needed are implemented internally. But we do the deployment of the instances hand-in-hand with SevOne support.

The initial setup is complex by nature but comparatively, it is simple when I consider a few of the other vendors that I have seen. Our deployment took between three and six months to complete.

When we deployed it, nine years ago, it was on a peer-to-peer architecture with physical machines. We slowly added a few instances to cover its predecessor. We continued adding appliances and within a year or two, we doubled the estate. Then year after year, we have been adding 20% to 30% to it.

I wasn't involved with setting up our production version, but we recently got a lab version. One of my colleagues got involved with SevOne support to install it, but I was involved in adding new devices, and that was pretty simple.

In terms of implementation, you just put up a VM, get the license, install it, and then add the devices. It's as simple as that.

We had to get in touch with support because there was one technical problem, something to do with MySQL, but other than that we didn't need any help. We were already using it in production and were familiar with it.

We don't really need to do maintenance on it at all, unless there is a bug and we need to get in touch with support.

It was simple as the environment wasn’t configured tightly (no ACLs, etc. to battle). There were some firewall rule changes where we needed to get to the DMZ devices we measure, but that moved quickly here.

The installation is fast and straightforward because you only need to configure the network interface with the proper IP to get the system up and running. It's really quick, just like flipping a switch.

The total deployment time depends on the customer's environment. It takes a little time to set up high availability and configure some aspects of the labor interface, but you can finish all the configuration in a day.

Some of our customers request integration with ITSM tools like Service Cloud. For a typical engineer, it isn't easy, but it's not that difficult, either. Some other solutions on the market have built-in integration with ITSM, but you need to use the command lines to integrate SevOne. 

We have been deploying to various customers over the past three years. we face some challenges in the SD WAN space but with LAN, WAN Wi-Fi and Netflow deployments.

The initial setup was straightforward. 

I don't know that we've ever finished the deployment. The tool is flexible so we're always trying new things. But getting it off the ground and running and alerting, I would say took about a month and a half to two months.

We deployed it in parallel to our existing monitoring tools and then took devices out of our existing monitoring tools as we proved that they were inside of SevOne.

When I joined, I started using SevOne and it was already implemented. We have done some version upgrades and configurations. I am just managing it because it was already running on-premises.

I was the sidekick for the setup but it seemed to be pretty easy. I had installed, from setup, HP OpenView systems with four D80 servers around the world. The SevOne environment was pretty good. We were small at the beginning.

Without the planning and everything, just when we got the devices and turned them up, it took around a week or two. We were in our own little lab, testing.

We had a database and we were taking Cisco devices first. Once we had all key indicators identified that they wanted to monitor, we did it. Then we slowly brought in each vendor with the certified files and checked them as we imported them. It was a good plan.

Straightforward I must say… Just get the appliance set up as a vanilla installation in the management systems. It’s sort of plug-and-play. It covered 75% of the network devices and servers farms out of box from day one.

I was not involved in its initial setup. For its maintenance, we've got two people in the US and two people in the Philippines who help us. They do network monitoring. The two people in the Philippines work part-time on it because they also support other tools. So, we have three people in total for 8,000 devices.

The tool’s setup was easy. We were able to onboard two major customers within two months of the product’s deployment. The overall deployment took around three months to complete.

I deployed SevOne on a virtual machine a couple of years back. The deployment was easy and straightforward. The installation wizard helps, giving you all the details of what is happening. There was no confusion. And it was fast as well. It took roughly two hours.

Someone from our deployment team helped me. He told me to just "apply this, do this, do that," apart from what the wizard showed me. I believe he was in touch with the SevOne guys.

The initial setup was pretty straightforward. We knew that the biggest hurdle we had to overcome was the Juniper compatibility, so that's where we focused the resources in the planning.

The means of actually getting it installed, upgrading the software, and then actually discovering the network worked as expected. It crawled, it discovered, and it did everything we needed it to. It just needed to be tuned for a 100% Juniper network.

Of course, the Juniper tuning took many hours of post-sales engineering support as well as a resident engineer. It took a lot of work on the SevOne side to actually get it to that point.

In total, the deployment took approximately three months.

In a standard solution, the instalation is very simple. In our case, we decided to integrate SevOne with an external database (an external application). All network devices devoted to that application should be automatically inserted into SevOne database.

The integration interface was the part of the solution that was performed by a third-party integrator in cooperation with SevOne.

Easiest deploying product I have ever worked with. It's intuitive. I used to be a Unix admin, and I haven’t done this deployment before, yet I'm able to find data as I need.

The set-up of the basic monitoring is straightforward, but customizing for special needs, such as calculation pollers, takes some effort.

The product was set up and installed by SevOne technicians. So, initial setup was very straightforward.

I wasn't involved in the initial setup, so I don't know.

Setup was very complex as there were issues with the device pipes. We needed a lot of intervention and technical assistance.

The initial configuration is very simple to implement could say it's something like Plug and Play, this solution is very user friendly and you are increasingly making improvements , many of them taken into account users

It was pretty straightforward.

I didn’t do the setup.

Setup was straightforward.

The initial setup was straightforward. Because initial solution design is very important, planning the initial setup with respect to you own environment is key. Ensure that all required IP connectivity and product specific UDP/TCP ports are open and available.

Pretty straightforward, but complex due to the size of our organization. This is not an issue with Sevone.

Initial setup was very smooth; we used a virtual appliance.

The initial setup was straightforward. It was simple and quite intuitive.

Initially, we wanted a specif look and feel regarding our SevOne solution. That took some extra time, but that's to be expected. In general, we got some useful information right out of the box with SevOne. Overall, it's easy to set up.

Setup was simple. It was not that complex because one server, one appliance would be the performance server and another would be a high availability server. The selection part was smooth.

But creating a policy, thinking with LDAP, that part takes some time, but in a good way.

Initial setup is straightforward.

Very easy to setup the first installation. It is easy and fast to achieve the basic level.

The setup is straightforward and is very flexible. Adding an appliance is very simple and easy to do.

I did not set up the system as it was done years ago and I just maintain it.

I'm not involved in deployment.

Complex for the MIBs.