In terms of the initial setup, you have to learn a little bit of Juniper voice command. If you have learned Juniper voice command, then everything will be in a similar pattern. That makes it quite easy. That said, for the first one or two days, you need hands-on training. Afterward, it is very easy.

I'd rate it four out of five in terms of ease of setup. It only takes a half-hour for configuration.

The initial setup is very easy and straightforward. I have taken remote assistance many times from end customers. Basic, newly trained people were able to troubleshoot, provide me with access and commit confirm is key feature to help to check configuration without on-site access configuration can be reverted back to original.

Juniper normally does public TSB, KB and other documentation which help customer proactive fix the newly hit PRs or Security updates in proactive manners, which help customers to avoid bugs and scalable and high performance. 

I would rate my experience with the initial setup a three out of ten, where one is easy and ten is difficult. 

The setup was also a bit complex, but we received good training for it.

The initial setup is not very complex, but it is not very simple. We need to have some expertise to do it. Cisco has a Setup Wizard that we can use. Juniper doesn't have it. We need to have CLI expertise.

Once we know what to do in our use case, it is very simple. Juniper’s cloud solutions are not well known. They have some issues. They are still dependent on hardware architecture. The cloud solution does not perform well.

The solution’s initial setup process is easy.

The initial setup took about a day or so. We had help with the process. A third party assisted the team.

We have a couple of engineers that can handle maintenance tasks as needed. We handle maintenance internally. 

The initial setup of Juniper Enterprise Routers is complicated.

The initial setup is straightforward.

The installemnet is easy to find on the portal. Joining the portal and navigating through it has become straightforward for me. When deploying Juniper switches for customers, the first step is to discuss their requirements and recommend any modernization or changes needed. The next steps involve addressing specific features, discussing network topology, and optimizing costs for the project. 

The initial setup for Juniper's MX Series routers can be straightforward if you prefer manual configuration. We typically connect via console, load our configuration files, and get our network up and running. We haven't used automated configuration tools because they might not have been available when we started. Sometimes, when you are used to a particular setup, it is challenging to switch to a new approach.

The solution is simple to set up. it's not overly complex. 

I'd rate the process of implementing a five out of five in terms of ease of the process. 

The initial setup is not very easy. It's not complex either. It's in the middle between easy and complicated.

If you are configuring MX or 80, if you know what you need to configure and if you are configuring the data center, deployment can take one day.

However, usually, you don't know what the customer needs or you don't know which direction of configuration you can use. For example, you can configure interfaces like virtual interfaces or sub-interfaces. It looks the same, however, they have some inside configurations that take longer.

So for these devices, you should analyze for big devices for data centers and internet service providers, you should analyze what kind of configuration you do before so it'll take more time than configuration.

Setting up Juniper MX Series Routers is generally straightforward. It takes a few hours to deploy it.

The solution is simple and straightforward. It is not complex at all. I'd rate it a three out of five in terms of ease of setup. 

The last time we deployed Juniper was six months ago and we had a pretty good time. After six months, we replaced all the requirements with the latest version of Juniper and it took, with migration, maybe three hours. It was easy.

We have four people on staff that handle deployment and maintenance. These include an engineer, a specialist, and a person well versed in analysis. 

The initial setup was not a very complex process and took three weeks. It went according to the plan.

The initial setup is not too complex. It's actually pretty straightforward. However, the level of difficulty of the implementation depends on the complexity of the customer. Deployment could take anywhere from a week to two weeks depending on the client's requirements and their company's own complexity levels.

Implementing Juniper MX Series Routers can be easy or complex, depending on each situation and whether firmware needs to be updated or if there are any bugs.

This solution is not difficult to deploy. I would say that it is straightforward. However, the first time somebody does it, they might find it difficult to deploy and configure. This is because they aren't familiar with it. When somebody has the proper training and hands-on experience, it is not that difficult.

If the high-level design and low-level design is in place, and the high availability deployment areas are ready, then it will take approximately two hours to deploy. This time includes production testing that avoids downtime, and we also consider the In-Service Software Upgrade (ISSU).

Where I am working now, it is very easy because we have all of the templates. It doesn't take much time. I can imagine that in some enterprise environments they take longer because they are lacking the technical hands, or the tools, or the templates.

I found the initial setup a little bit hard because I was learning it from the Juniper website as I was doing it. The deployment took about two months.

The initial setup is straightforward. They have a lot of tools to do the setup. They are also either remote or cloud-based for very technical people, with hands-on scripting, too.

There are Switches where you don't need to do anything and others where you have to do a lot of things because the environment is complex. So you don't know how long it will take.

But the deployment is easy enough. The issue is that the networks get more and more complex so you have to take care of all the details in the programming if you are setting up a complicated network. If you are setting up an easy network, you plug it in to the power and you are there.

Our experience is different for different Juniper boxes. The installation was okay for MX100, but it was not that easy for MX200. For QFX5120, it was a nightmare.

We are not an end-user provider. We are a backbone company. Internet exchange is the central point for the internet in every region. We have connected around 10 customers on one router. We have three routers in our network.

The initial setup wasn't complex. It was straightforward. We didn't have any issues with the initial implementation.

When you are not familiar with this solution it seems difficult to configure and deploy. Once you have the proper training and hands-on experience, it is not that difficult.

For me, the initial setup is straightforward. I configure the hostname, use the interfaces, and configure the routing. All of this stuff should be included in the low-level design. We have developed a template to make this easier.

If everything is ready, including the high-level and low-level design, then you can deploy this solution in approximately two hours.

The setup was very straightforward.

The initial setup was good, and there were no problems.

The setup for the solution was surprisingly straightforward. I think it was because we just migrated from a Cisco router. There were tools available on the internet that translated the Cisco commands to Juniper commands. So it was very easy to do and very straightforward to build the new configuration.  

The leaning curve was not very steep.  

The deployment took about two days working full-time and the only person involved in the deployment process was me.  

The installation is easy and it does not take very long.

The initial setup is very straightforward. On average, they take two or three weeks to deploy.

The initial setup is not complex. It will take not more than 20 minutes to deploy.

The initial setup is not complex for me because I have a Cisco background, and it did not take long to get used to Juniper. If somebody has worked with Linux or Unix then the hierarchy is not that different.

I would say that if somebody is coming from a background of Cisco and a bit of Linux, they won't have any problem. However, for people that I've seen who don't have a pure IT background, they have difficulties getting used to it.

The installation was easy.