Juniper MX and M series routing consulting

I’ve worked with BGP, OSPF and IS-IS for 25 years, and Juniper routing is one of my core focuses. I work on MX at the internet edge, in the core and at the data center boundary, and I still see plenty of M series routers that are overdue for replacement.

What I help with

BGP design and troubleshooting. Internet edge and multi-homing, route policy, communities, prefix filtering, and the sessions that flap at 3 a.m. for no obvious reason.

IGP design. OSPF and IS-IS area design, metrics, and cleanups of IGPs that have grown without a plan.

Edge and peering. Dual-provider edges, transit and peering policy, and keeping full tables healthy on the hardware you have.

Data center interconnect and edge. MX as the boundary between an EVPN-VXLAN fabric and the WAN or internet.

M series to MX migrations. M series routers are long past end of life, and their configurations usually reflect years of incremental changes. I audit the existing config, translate what matters, drop what doesn’t, and plan a cutover that can be rolled back.

Configuration reviews. A second set of eyes on routing policy before a change, or a full review of an inherited network.

How engagements usually work

Troubleshooting is usually remote and hourly. Migrations and redesigns are scoped as a project with a written plan, a maintenance-window runbook and a rollback path.