We integrate this solution for our clients. 

If the customer's site is ready—meaning the power pooling and environment are ready—the deployment time depends on the criteria. For instance, in a Provider Edge (PE) scenario, i I've  designed and tested the configuration in my lab, or if I'm replacing a similar device for the same customer and only need to change the IP address, it can be quite quick. It's important to ensure that the software is on the recommended release. 

The hardware specifics, like next-generation routing engines, also play a role. Typically, it takes about 30 minutes for the initial upgrade and reboot. If it's a manual configuration, the service-wide installation takes another 30 minutes. So, for a straightforward installation with pre-configured integration, it's typically a day-one job. 

In a data center scenario, additional considerations like network intent come into play, and it can take a few hours. So, in a data center context, whether it's for Internet edge, data center interconnect, or any other node within a data center, the placement of the MX router varies. The time it takes depends on the deployment model. For experienced teams with well-planned setups, it's generally a one-day job.

If the hardware is redundant, then you have some time to do any upgrade or to add cards. Based on the deployment again, there are minimal items that need maintenance, like the paint-free and filter, which you have to change. That is readily and easily available from Juniper. 

So, as a partner, we actively maintain with the customer, planning and giving them regular maintenance plans, especially for the environment type of stuff. That's what customers normally do. If they are managing it, you don't see any issues arising.

The deployment was a team effort. We started with ten people and went up to forty. Initially, when we did a lot of customer migrations using Juniper, the initial configuration was quite easy. But it depends on how many customers, how many VPNs, and all that stuff are being migrated. So in terms of timing, the minimal configuration, just making the router up and running, maybe took around two hours or more. 

We deployed it for quite a big project, so it took some time to set up, especially for a nationwide ISP.

We needed a good plan, the right environment for the devices, and then we proceeded with the deployment.

We had about 14 staff members for for the deployment and maintenance, mostly engineers, and a couple of managers.

As for the deployment steps, I turn on the power cable on Juniper MX Series Routers and configure the system on the solution.

For deployment, it takes 20 to 30 minutes to install the system. Then you can configure the link to connect to another device.

When you want to install something on a version and cannot do it, you can check on another version. However, it would be best to do it during downtime when people are not working.

We worked with a distributor in order to deploy the product. We were provided training as well. 

We had some help from the Juniper engineers in setting Juniper Enterprise Routers up. Our implementation expert moved to another company and we are having a difficult time finding a replacement.

We have four to six engineers that are experts and they are supporting this solution.

I find it to be one of the most feature-rich aspects, particularly appreciating the synchronous configuration, making it straightforward for me.

In terms of manpower for deployment, it can vary based on the complexity of the project and the current market conditions. In the current situation in Ukraine, finding new engineers for the team can be challenging due to the ongoing changes in the market and the need for maintenance.

We handled the deployment in-house. We did not need outside assistance from integrators or consultants. 

I have hands-on experience deploying this solution for our customers.

I deployed this solution on my own.

It is not a huge installation. You just need two people for its installation. My partner and I have 25 years of experience in the business, and we install it ourselves. We also take support from a system integrator. For the second level of support, we use JTAC.

As integrators, we help advise clients on the best ways to handle implementations and can assist with the process as well.

We deploy this solution ourselves, and we are careful to take steps in order to avoid downtime. We also take the In-Service Software Upgrade (ISSU) into consideration.

At one point we did use the help of an integrator but it was some point later after the initial configuration was done. We did that initial configuration directly from what we already had, using only the translation tools.  

Because we were not migrating. We were not inventing anything new. We were not building anything new. We were just migrating. That was why it was so easy. We already had the configuration, and we just wanted to deploy it to the new equipment. It was not custom, so it was simple.  

We have certified engineers that do the implementation and maintenance of the solution.

We have engineers who are certified by Juniper and they deploy the routers for our customers.

I have deployed several of the routers on my own.