← Back to projects
PROJECT

Manufacturing company in Hangzhou | Phased segmentation of a /23 flat network

The primary /23 network had grown to roughly 379 used addresses, with office, production and wireless access sharing the same boundary. The project kept the existing subnet as a migration anchor and introduced four controlled zones without forcing a big-bang production cutover.

HangzhouManufacturingNetwork redesign / four zones / phased cutover
01

Project context

The site had expanded for years around a single /23 network, with roughly 379 addresses already in use. IP allocation and access points were not centrally governed, wireless clients could enter the internal network directly, and office and production devices shared the same security boundary. The challenge was not simply to create VLANs; it was to expose undocumented dependencies and move the environment toward a maintainable model without disrupting production.

02

Objectives

  • Separate office, production, server and guest wireless traffic into clear operational zones.
  • Retain the existing /23 network during the transition instead of renumbering the whole site at once.
  • Identify ERP/MES, database, directory, printing and scanner dependencies before restricting cross-zone traffic.
03

Scope baseline

01

Inventory of core/access switching, APs, address usage and critical paths.

02

Four-zone VLAN, gateway, addressing and wireless boundary design.

03

Layer-3 and firewall relationship mapping with required cross-zone flows.

04

Phased migration, business verification, rollback conditions and as-built documentation.

04

Implementation and control

  1. 01

    Capture the existing address plan, uplinks, AP connectivity and business-critical endpoints, and mark devices that cannot be changed during production hours.

  2. 02

    Classify traffic as required, restricted or isolated; treat ERP/MES, database, directory, printing and scanning flows as explicit acceptance items.

  3. 03

    Use the existing /23 as the transition base while moving new zones in controlled batches rather than renumbering the plant in one window.

  4. 04

    Validate lower-risk areas and guest wireless first, then move office, server and production boundaries in stages.

  5. 05

    Close the project with before/after diagrams, VLAN/IP records, key rules and a list of any remaining historical exceptions.

05

Risk and change control

R01

Legacy or statically addressed equipment may depend on undocumented paths, so discovery comes before enforcement.

R02

Guest and employee wireless separation requires addressing and access-control changes, not just an SSID rename.

R03

Least-privilege rules are introduced only after application validation; broad blocking is not used as a shortcut.

06

Acceptance and handover

  • Office, production, server and guest wireless zones operate as distinct boundaries with required business paths preserved.
  • Critical ERP/MES, database, directory, printing and scanning paths are verified.
  • Each migration batch has documented rollback conditions and change records.
  • As-built network diagrams, addressing plans and key policy records are handed over.

Key deliverables

Before/after network diagramsVLAN / IP / gateway planCross-zone flow and key-port matrixCutover, verification and rollback record

Planning a similar project?

Share the current environment, business impact and target outcome. We will confirm scope, dependencies and delivery boundaries first.

Discuss a similar project →