Needs review and network map
We look at users, services, existing hardware and internet links, then draw the physical and logical network map.
Start here
Free Audits 5Urgent help
Emergency 4Ongoing support
Managed IT 5Projects
Servers & Hosting 6 Network & Virtualization 9 DevOps 5 Security & Recovery 5 Hardware & Licensing 2Find out where your servers, security, backups and performance stand, at no cost.
Server down, network out, site hacked or data lost? Call us now.
Monthly network and server support with response times written into the contract.
Setup, configuration, management and migration of Linux and Windows servers, panels and mail.
Network design and cabling, MikroTik, VoIP, branch links, virtualization and private cloud.
Networking & communications
Virtualization & cloud
Containers, Kubernetes, automated delivery, infrastructure as code and observability.
Server hardening, firewalls, backup and DR, ransomware recovery and incident forensics.
Advice, supply and installation of servers and network gear, plus genuine enterprise licenses.
Start here
Urgent help
Ongoing support
Projects
Most office networks grow one switch at a time, and after a few years nobody has an accurate map. Our network setup work starts with a needs review and a logical design covering VLANs, IP addressing and uplinks. Then we configure the hardware and hand over a documented network your own staff can troubleshoot.
Business network setup is the service of designing, configuring and documenting a company's internal network, from the first needs review to a tested handover. It suits offices moving to new premises, and networks that grew one switch at a time until cameras, guests and staff all ended up on one flat segment. PikoSystem draws the physical and logical network map, designs VLANs and the IP addressing plan, configures Cisco, HPE Aruba or MikroTik switches and the edge router, sets up automatic failover when there are two internet links, and separates staff and guest Wi-Fi. Work that causes downtime is scheduled in agreed windows. You receive network diagrams, a switch port list, configuration backups for every device and a final test report, so your own staff can troubleshoot the network.
We look at users, services, existing hardware and internet links, then draw the physical and logical network map.
We separate the network by role: staff, servers, cameras, VoIP and guest Wi-Fi. IP ranges and DHCP scopes are documented.
On Cisco, HPE Aruba or MikroTik gear we configure access ports, trunks, STP and a management VLAN, then back up the final config.
We connect internet and private links to the edge router and set up NAT and routing. With two links, we configure automatic failover.
Access points get separate SSIDs for staff and guests, and we check signal coverage on site.
Port count and hardware class matter most. A single access switch is a very different job from a multi-floor network with a core switch, PoE cameras and two internet links. PoE budget is easy to overlook: access points, cameras and IP phones all draw from it, and that alone can change the switch model you need.
The second factor is what already exists. Unlabeled cabling or configs inherited from several past admins mean part of the work is discovery. VLAN count, Wi-Fi coverage, branch links and after-hours work also change the scope. A list of current devices with model and firmware version makes any estimate more accurate.
Cisco Catalyst fits teams that already know IOS and need stacking and 802.1X authentication. HPE Aruba CX offers similar features and can be managed through Aruba Central. MikroTik CRS switches handle VLANs and LACP on a smaller budget, as long as the config keeps switching in the hardware chip instead of the CPU.
Ubiquiti UniFi suits small offices that want switches and Wi-Fi under one controller. Mixing vendors is fine because 802.1Q and LLDP are standards. What matters more is that every switch is managed: an unmanaged switch gives you no VLANs and no loop protection.
The classic one is a flat /24 holding every device. Add cameras and IP phones, the DHCP pool runs out and broadcast traffic reaches every machine. Using VLAN 1 for management and as the native VLAN on trunks also weakens the separation you designed.
Missing BPDU Guard on user ports is common too. Someone plugs a desk switch in with two cables and the loop takes the office down. DHCP Snooping stops a stray home router from handing out wrong addresses. On Cisco gear, forgetting copy running-config startup-config means the first power cut quietly undoes your changes.
New users, printers and cameras keep arriving, and if the port list and IP plan aren't updated you are back where you started within a year. Recording each change in NetBox, or even a shared spreadsheet, prevents that.
Firmware updates, automatic config backups with Oxidized and SNMP monitoring of uplink ports surface problems before they become outages. If nobody in-house owns these tasks, they can be written into a support contract.
We visit the site or review the current network remotely and walk through requirements with you.
You receive the design, a hardware list and a work estimate. Existing equipment is reused wherever it fits.
We install and configure the hardware. Changes to a live network happen only in time windows agreed with you.
We test the network, hand over documentation and show your team routine tasks such as adding a user port.
Usually some of it, yes. During the first visit we check each device's model, firmware and condition. We only suggest a replacement when a device lacks something the design needs, such as VLAN support or remote management.
Yes. If your network is already designed and you only need Cisco switch configuration or a review of the current config, we do just that. The existing config is backed up before any change.
Work that causes downtime is scheduled for quiet hours or weekends. Every outage window is agreed in advance, and a rollback path is ready before we start.
We can give you an exact hardware list to buy yourself, or handle supply and installation. Either way, models are chosen for what the network actually needs.
Related searches
Quote
A few lines on where things stand and what you want is enough. An engineer calls you back, not a sales rep.