--- title: "Enterprise LAN, WAN and Wi-Fi" description: "Campus switching, WAN design across multiple carriers, wireless surveys and design, network access control and lifecycle refresh." url: https://www.expandware.com/services/networking/enterprise-lan-wan-and-wifi/ section: "Services" topics: ["Networking", "IEEE 802.1X", "Wi-Fi 7", "Wi-Fi 6E", "Cisco Catalyst"] publisher: "Expandware Private Limited" --- # Enterprise LAN, WAN and Wi-Fi Campus switching, WAN design across multiple carriers, wireless surveys and design, network access control and lifecycle refresh. Campus and branch networks that keep working when a link fails. Users notice the network only when it fails, and in most offices it fails at the edges: a single internet circuit, an overloaded access point, a switch nobody has patched. We design campus and branch networks with diverse carriers, redundant uplinks, wireless planned from a site survey and access control that knows which devices belong, then document them so they can be supported by more than the person who built them. Where it usually starts: - A branch stops trading when its one internet circuit goes down. - Wi-Fi complaints arrive from the same rooms every week. - Network equipment is past its end of support. - Anyone can plug into a network port and reach internal systems. What is included: - Campus switching: Core, distribution and access layers designed for resilience. - WAN design: Multiple carriers, diverse paths and failover tested in practice. - Wireless: Predictive and on-site surveys, with design and tuning for density. - Network access control: Devices authenticated before they reach the network. - Refresh and migration: End-of-support equipment replaced with minimal disruption. - Documentation: Diagrams, configurations and addressing kept current. Where it sits: Campus and Wi-Fi networks are the users and sites edge of the networking architecture: the switching and wireless people connect to in offices, linked to everything else through the WAN. Decisions to settle early: - Cloud-managed or traditional. Cloud management suits many sites and lean teams; traditional management suits complex campuses. Licensing often tips the balance. - Which wireless standard. The newest standard is not always needed. Devices in use and density decide. - Standard site design or bespoke. A standard design makes every site supportable the same way. Exceptions are kept for sites that truly differ. How the work runs: Survey, Sites, coverage and circuits. Design, Topology, wireless and access control. Deploy, Staged cutovers out of hours. Document, As-built diagrams and configurations. How it is bought: - A fixed-fee assessment: We survey a sample of sites for coverage and circuits and inventory equipment and support status. You receive the findings, a standard site design outline and a fixed price for the rollout. - A fixed-price build: Design, equipment refresh, wireless placement, access control and staged cutovers for the sites in scope, priced per site. - Running it afterwards: Sites can then be supported by your team with as-built documentation, or monitored and maintained by us monthly. Worked example, stores that stop when one circuit fails. Say a retail chain's stores each depend on a single internet circuit, Wi-Fi in the stockrooms drops out, and the switches in many stores are past end of support. - Survey: We survey a sample of stores for wireless coverage and circuits, and record the equipment and configuration at every site. - Design: A standard store design adds a second circuit from a different carrier, wireless placed for the stockroom, and access control on network ports. - Deploy: Stores are cut over out of hours in planned waves, and each is tested for failover before staff arrive. - Document: Every store gets as-built diagrams and automatic configuration backups, and the refresh plan covers the remaining equipment. At the end, a failed circuit no longer stops a store, the stockroom Wi-Fi works, and any engineer can support any store from the same documentation. (An illustration, not a client account.) What you have at the end: - Site surveys and wireless heat maps: Coverage, capacity and interference measured at each site, with access point positions marked. - Network design and addressing plan: The switching, routing, wireless and addressing design for each site and the links between them. - Cutover plans for each site: The steps, timing, tests and rollback for moving each site onto the new network. - As-built diagrams and configuration backups: Drawings and configurations that match what is installed, with configurations backed up automatically. - Lifecycle and refresh plan: Support dates for every network device and a schedule for replacing each before its support lapses. Standards and platforms worked with: IEEE 802.1X, Wi-Fi 7, Wi-Fi 6E, Cisco Catalyst, Cisco Meraki, HPE Aruba Networking, Juniper Mist, Fortinet, Ekahau. Where it goes wrong, and what we design out: - One circuit per site. A single carrier is a single point of failure. Sites get diverse circuits, tested in practice. - Wireless placed by guesswork. Access points mounted where it was convenient leave dead zones. Placement follows a survey. - Open network ports. Any device plugged into the wall reaches internal systems. Ports authenticate devices first. What it changes: - Branches that keep trading. Diverse circuits and tested failover turn a carrier outage into a non-event. - Wi-Fi that covers the building. Designed from a survey, so coverage and capacity match how rooms are actually used. - Only known devices connect. Access control keeps unknown devices off the network. How you will know it is working: - A failed circuit does not stop a site. - Wi-Fi complaints stop coming from the same rooms. - Unknown devices reach nothing of value. - Every site has current diagrams and configuration backups. Who you work with: - Network architect. Designs the standard site, wireless and access control. - Wireless engineer. Runs surveys and designs and tunes coverage. - Field engineers. Install equipment and cut sites over out of hours. What we need from you: - Floor plans for the sites in scope. - Access to current network equipment. - Circuit contracts and carrier details. - Local contacts at each site for cutover nights. Common questions: Q: Do we need a wireless survey? A: For anything beyond a small office, yes. Walls, materials, interference and user density decide where access points belong, and a survey finds that before installation rather than through complaints afterwards. Q: How many internet connections should a branch have? A: At least two, from different carriers over physically different paths where possible, with automatic failover. One circuit is a single point of failure for the whole site. Q: Can you refresh equipment without downtime? A: Mostly. Changes are staged out of hours with tested rollback, and sites with redundant uplinks can often be upgraded with no visible interruption. Q: What is network access control? A: A system that checks a device's identity and health before letting it onto the network, usually through 802.1X, so an unknown laptop plugged into a meeting room port reaches nothing. Q: What is the difference between a predictive and an on-site wireless survey? A: A predictive survey models coverage from floor plans and building materials before any access point is installed. An on-site survey measures real signal and interference in the building. Most designs use a predictive survey to plan and an on-site survey to confirm. Q: Should we move to cloud-managed networking? A: Cloud-managed platforms make many sites easy to run from one dashboard and suit organizations with lean network teams; traditional management can suit complex campuses better. We compare them on your sites, your team and the licensing model, which is often the deciding factor. Q: Is Wi-Fi 7 worth deploying now? A: In demanding spaces it can be, provided your devices will support it during the equipment's life. For many offices, Wi-Fi 6E is enough. The decision follows the survey and the devices you expect to use, not the newest standard. Q: How do you secure network ports in offices? A: With network access control using IEEE 802.1X, so a device must authenticate before it reaches the network. Devices that cannot authenticate, such as printers, are identified and placed in restricted segments, so an unknown device plugged into a wall port reaches nothing of value. Often paired with: SD-WAN and SASE, Monitoring and network operations, Network security. --- Canonical page: https://www.expandware.com/services/networking/enterprise-lan-wan-and-wifi/ Site index for machines: https://www.expandware.com/llms.txt Full site text: https://www.expandware.com/llms-full.txt Expandware Private Limited. Inquiries: solutions@expandware.com, +92 (333) 32 11011.