Skip to content

Nepal Office Network, Phase 2: Full Fortinet Migration

By Bikram Bhujel

Network case study · September 2026

Nepal Office Network, Phase 2: Full Fortinet Migration

In March I split a flat office network into staff and guest networks on the existing Cisco equipment. In September the rest of the Fortinet equipment arrived, and I replaced the Cisco switches and standalone access points, added a camera network, and moved everything under one console.

PlatformFortiGate 91G · FortiSwitch 248E-FPOE · FortiAP 231K / 231F
CutoverSunday 20 September 2026, 12:00–19:00
My roleSole implementer on site: design, racking, cabling, configuration, testing, report
EnvironmentCIMMYT country office, Nepal
12 → 1Separately managed devices replaced by one console
92.9 MbpsMedian Wi-Fi download after, from 5.8 Mbps (different test devices)
3 networksStaff, guest and a new camera network
01 · Project overview

Finishing what the March upgrade started.

The March upgrade was a stopgap: only the new firewall had arrived, so I segmented the network on the existing Cisco switches and access points. It removed the biggest risk, a flat network shared by staff and guests, months before the full equipment was available.

Phase 2 replaced the remaining end-of-life equipment and brought the office onto the same design as the other country offices.

Read the Phase 1 VLAN case study

This post describes work I did in my role at CIMMYT. The network and equipment belong to CIMMYT; addresses, configurations, device names and the names of colleagues are left out on purpose. All figures come from my own project reports.
02 · Starting point

Four switches and eight access points, each managed on its own.

Before

Switches4 × Cisco Catalyst 2960X
Access points8 × Cisco Aironet 2702I, standalone
NetworksStaff and guest
Content filteringNone
Management13 devices, one by one

After

Switches3 × FortiSwitch 248E-FPOE
Access points7 × FortiAP, powered by the switches
NetworksStaff, guest and camera
Content filteringWeb, DNS and application control
ManagementOne console
03 · Network design

Separate networks with clear rules between them.

Staff networkInternet access with security profiles; staff can view the cameras, and nothing else crosses into the camera network.
Guest networkSized for many visitor devices, with one-day address leases. Guests cannot reach staff devices.
Camera networkNew in this phase. Cameras cannot reach staff devices.
LoggingInternet traffic is logged, and so is every blocked attempt to cross between networks.
AdministrationThe firewall can be managed only from inside the office, using named administrator accounts instead of a shared login.
InternetOne provider today; a second port is already set up for SD-WAN with health checks, so a second provider can be added without a redesign.
04 · Wireless design

One profile per model, no per-device exceptions.

  • One access point profile per model, so there are no individual settings to drift out of date
  • 2.4 GHz limited to channels 1, 6 and 11 at 20 MHz
  • 5 GHz at 40 MHz with automatic channel selection
  • The third radio on each access point used as a dedicated monitor for interference and unknown access points
  • Guest Wi-Fi shared with a printed QR-code sign
05 · Cutover and validation

One afternoon, then checks on a working day.

01
Upgrade the firewall firmware.

Moved to the current release before connecting the new switches.

02
Replace the switches.

Racked the FortiSwitches, moved every connection, and brought them under the firewall.

03
Replace the access points.

Mounted the FortiAPs, powered from the switches, and applied the model profiles.

04
Test filtering.

A peer-to-peer download on a staff computer was stopped with a block page pointing to the IT Service Desk; a blocked social media app was stopped at DNS level.

05
Fix what testing found.

One access point stayed offline; the cause was a cable damaged by rodents, which was replaced.

06
Refresh the records.

Port map, configuration backup and NetBox documentation updated on a working day.

06 · Results

Faster Wi-Fi, with an honest caveat.

From my migration report
MeasureBeforeAfter
Wi-Fi download (median)5.8 Mbps (4 tests)92.9 Mbps (6 tests)
Wi-Fi upload (median)22.8 Mbps49.7 Mbps
Wired downloadNot measured85.8–94.5 Mbps (7 tests)
The before tests were taken on phones and the after tests on a laptop, so treat the Wi-Fi comparison as indicative. Because of this, the plan for the next office requires the same laptop for both.
07 · Lessons

What I would keep, and what I changed afterwards.

01
An interim fix is worth doing.

Segmenting on old hardware in March removed the main risk six months before the full upgrade.

02
Physical problems hide behind logical ones.

The offline access point looked like a configuration issue and turned out to be a damaged cable.

03
Measure the same way twice.

Comparable before and after tests matter more than the size of the improvement.

Comments

Questions and corrections are welcome. I read every comment before it appears, and remove spam and promotional links.