Laurent N.

Context and challenges:

Objectives:

• Redesign architecture for high availability and HDS compliance.
• Migrate the last on-premise servers to the cloud.
• Industrialize deployments and hardening.
• Microsoft 365 identity/security governance.
• Improve backup and restore reliability.

Scope and key tasks

Think:

• Audit of flows, IT dependency mapping, risk analysis and exposure surfaces.
• HDS/non-HDS segmentation, trusted zones, interconnections, DRP/BCP.
• HLD/LLD architecture documents and migration plan.

Build:

• Standardized Windows 11/Linux VM templates (gold images) with hardening, agents, monitoring.
• Proxmox and VMware deployments (Hyper-V management if required).
• End-to-end Microsoft 365 integration: Exchange Online, Teams, SharePoint Online, Azure Entra ID (MFA, Conditional Access, governance).
• Veeam backup policy (retention, regular tests), automations.
• Internal/external DNS and OVHcloud integration (public zones, certificates).

Run:

• N2/N3 monitoring and operations, incident/problem management.
• Webex Contact Center administration (routing, queues, reporting).
• ITSM via GLPI, CMDB, operational documentation and runbooks.

Measurable results:

• Target architecture validated and compliant for HDS perimeters.
• Reduced provisioning thanks to standardized templates.
• Generalized MFA/Conditional Access coverage, reduction in identity incidents.
• Reliable backups (success rate and documented restore tests).
• Operational N2/N3 procedures and monitoring.

Technical stack:

Context and challenges:

• Modernization of the production network infrastructure.
• Replacement of core/distribution switches, critical service continuity (operations, ticketing, video, IoT), security, and performance.
• Migration ArubaOS 2019 → 2022 with configuration alignment.

Objectives:

• Replace core/distribution equipment and improve architecture reliability.
• Migrate and adapt configurations (VLAN, routing, security).
• Optimize performance and rationalize the addressing/DHCP plan.
• Ensure continuity and validate post-migration load.

Scope and key tasks

Think:

• Audit: L2/L3 topology, addressing, VLANs, DHCP, ACLs.
• Migration strategy 2019 → 2022, command/function mapping.
• Outage/rollback plan, port/VLAN matrices, acceptance criteria.

Build:

• Replacement of Aruba switches (core/distribution) and associated cabling.
• Porting/adaptation of configurations: tagging/untagging, SVIs, inter-VLAN routing, DHCP relay/options, ACLs, QoS.
• Address rationalization, standardization of conventions (naming, descriptions).
• Updated configuration documentation and diagrams.

Run:

• Controlled production deployment, phased by domain (VLAN/services), real-time monitoring.
• Continuity validation and load tests: latency, throughput, loss, failover.
• N2/N3 corrections, stabilization, skills transfer.

Results:

• Core/distribution migration without major interruption.
• Reduced convergence, decreased latency/errors, stabilized throughput.
• Simplified addressing plan, reliable DHCP.
• Updated documentation and inventory.

Technical stack:

Context and challenges:

Objective:

• End-to-end diagnosis and compliance restoration of a Ubiquiti UniFi infrastructure, with service continuity and lasting performance.
• Stabilize connectivity, eliminate micro-cuts.
• Reduce interference/airtime, improve roaming.
• Standardize SSID, security, and VLAN/DHCP management.
• Bring configuration and monitoring under control.

Scope and key tasks:

Think:

• Radio/network audit: coverage, channel overlap, RSSI/SNR, airtime, co/adjacent interference, client density.
• UniFi parameter review: TX power, channel width, SSID, band steering, 802.11k/v/r based on compatibility.
• Optimization plan: non-overlapping channels, power adjustment, AP load balancing.

Build:

• AP reconfiguration: 2.4/5 GHz plan, 20/40 MHz width, calibrated TX power, PMF, WPA2-Enterprise/WPA3 if supported.
• SSID and VLAN rationalization, client isolation, consistent DHCP.
• Roaming adjustments: enable 802.11k/v/r in compatible zones, disable if legacy terminals are unstable.
• Controlled firmware and UniFi Network Controller updates, backups, and runbook.

Run:

• Field measurements: light heatmaps, iPerf/latency/throughput tests, roaming path.
• Post-change monitoring: association rate, average RSSI, throughput/errors, interference alerts.
• Iterative corrections and skills transfer.

Results:

• Malfunctions resolved, stability restored.
• Airtime and reassociations reduced, smooth roaming.
• Improved peak throughput and latency.
• Standardized and documented configuration.

Technical stack: