Enterprise Network Services
Connect sites, systems and people without compromising resilience.
Architecture, multi-site connectivity, network security and operational support designed around business-critical communication.
Discuss enterprise networking →Senior expertise focused on what the organisation needs to protect and improve.
Architecture, multi-site connectivity, network security and operational support designed around business-critical communication. Every engagement begins with the operating context, evidence and a clearly defined outcome.
A practical, accountable service.
Architecture and resilience
Assess topology, capacity, segmentation, monitoring and application dependencies.
Connecting sites
Design resilient communication across offices, plants, mines and commercial locations.
Secure operations
Strengthen remote access, perimeter controls, visibility and incident readiness.
Clear steps. Visible decisions.
What sits on the network
Worth stating plainly, because it explains why network design decisions have consequences far outside IT.
A modern corporate network carries business systems and user traffic, and alongside them it carries voice, surveillance cameras, access control, building management, wireless, guest access and, on industrial sites, production equipment. Each of those has different traffic characteristics, different security requirements and a different owner.
On a flat network they all share a broadcast domain and they can all reach each other. That is the situation in most mid-market environments and it is rarely a decision anyone made. It happened because each system was added when it was needed and the network was whatever was already there.
Segmentation is the structural fix and it is usually the highest-value network work available. Separating servers, users, guests, voice, cameras, access control, building systems and operational technology into their own segments, with routing controlled at the firewall, changes both the security position and the troubleshooting.
The services
Network architecture
Design and documentation: topology, VLAN structure, addressing, routing, resilience and capacity. Covered on network architecture.
Network security
Firewalls, segmentation, remote access, wireless security and the rule review nobody has done since the firewall was installed. Covered on network security.
Multi-site connectivity
Links between sites, SD-WAN, failover and the arrangements that work when one site is a mine or a depot rather than an office. Covered on multi-site connectivity.
Corporate VoIP
Telephony over the data network, hosted PBX, SIP trunking and Teams calling. The quality of service configuration that makes it work is a network job rather than a telephony one. Covered on corporate VoIP.
Commercial CCTV
IP surveillance, sized and segmented properly, with POPIA footage governance. Covered on commercial CCTV.
Biometric access control
Access systems with OSDP-secured readers and POPIA-compliant template handling. Covered on biometric access control.
Cellular signal solutions
In-building mobile coverage where the building fabric blocks it. Covered on cellular signal solutions.
Wireless
Design for the use rather than for coverage. A wireless network adequate for laptops will drop voice calls during roaming and will not carry a warehouse full of scanners. Access point placement, channel planning, roaming configuration and capacity are separate exercises from a coverage heat map.
Structured cabling
Cable, containment, patching and labelling, to a standard, documented. Unglamorous and it is what everything else sits on. Retrofit into occupied buildings is usually the schedule constraint on any network project.
What tends to be wrong
Consistent findings across the environments we assess.
No documentation
No topology diagram, no VLAN or addressing record, no rack layout, no patching schedule. The network is understood by one person who is not always available and who did not build all of it either.
Configuration drift
Switch configurations that diverged from a standard because a fault was fixed in a hurry. Without configuration backup and periodic comparison against a baseline, the estate becomes a set of individual devices rather than a system.
Firewall rules nobody can explain
Rules added for projects that ended, kept because nobody can prove they are unused. Rule bases grow monotonically unless something forces a review.
Wireless designed for coverage rather than for use. Enough signal everywhere and not enough capacity anywhere that matters, with roaming configuration left at defaults so handsets cling to a distant access point.
Single points of failure that nobody chose. One switch feeding a floor. One uplink with no failover. A core switch with a single power supply. These are usually cost decisions made once and never revisited as the site grew.
No monitoring of the things that fail quietly. Interface errors, optical light levels, PoE budget headroom, failover link status. A backup link that has been down for weeks is discovered when the primary fails.
What Namandla delivers
Assessment
Topology and configuration discovery, documentation of what actually exists, capacity and error analysis, security review and a written position with findings ranked by consequence.
Design
Topology, segmentation, addressing, routing, resilience and wireless, documented to a standard someone else can maintain.
Deployment
Switching, routing, firewalls, wireless, cabling and the physical security and voice systems that sit on the network.
Support
Configuration management, change control, monitoring, vendor and carrier liaison and fault resolution under the response commitments on managed IT services.
Documentation kept current rather than produced once at handover.
Onsite work is Gauteng. Design, configuration and remote support run nationally.
Common questions about Enterprise Network Services
What does enterprise networking cover?
Switching, routing, wireless, firewalls, remote access, connectivity between sites and the structured cabling underneath. On a corporate site it also covers the voice, surveillance, access control and building systems that share the same infrastructure.
The reason those last items belong in a network conversation is that they are network devices with their own traffic profiles and security requirements. Treating cameras and access controllers as facilities equipment rather than as networked systems is how they end up on the same segment as your finance servers.
Why does network segmentation matter?
On a flat network every device can reach every other device. Segmentation separates servers, users, guests, voice, cameras, access control and operational technology, with routing controlled at the firewall.
It changes the security position, because one compromised endpoint no longer has a path to everything. It also changes troubleshooting, because traffic is separable and a broadcast storm on one segment does not take the site down. It is architecture rather than a product purchase, which is why it rarely appears on a shopping list despite being the highest-value work in many environments.
Our Wi-Fi is unreliable. What is usually wrong?
Most often the design was for coverage rather than for use. Enough signal everywhere is not the same as enough capacity where people work, and default roaming configuration makes devices cling to distant access points instead of switching.
The other frequent causes are channel overlap from too many access points on the wrong channels, insufficient uplink capacity from the access switch, and no separation between corporate, guest and device traffic. A wireless survey against actual usage rather than a coverage heat map is what distinguishes these.
Do we need SD-WAN?
It earns its cost where you have several sites, more than one connectivity type per site and a genuine need for application-aware routing and automatic failover. On two sites with a single link each, a simpler design is usually better value.
Covered in detail on multi-site connectivity. The honest position is that SD-WAN is frequently sold into environments where the actual requirement is a second link and a working failover configuration, which costs considerably less.
Can you take over an undocumented network?
Yes, and it is most of what we inherit. Discovery, configuration collection, topology mapping and documentation is the first phase of any takeover, before anything is changed.
We do not make changes to a network we have not mapped. The discovery phase reliably finds things nobody knew about: an unmanaged switch under a desk, a rule permitting access nobody intended, a link running at a hundred megabits because of a duplex mismatch set in 2019.
How disruptive is network work?
Design, documentation and configuration collection are non-disruptive. Physical work and cutover need planned windows, usually outside business hours, with a rollback plan.
Cabling into occupied buildings is the item that most often sets the schedule. Where containment exists, work moves quickly. Where cable has to be run through live office space, a working warehouse or an area with permit requirements, the survey establishes a realistic timeline rather than an optimistic one.
Do you supply the internet connectivity?
No. We design the connectivity, specify what is needed, help you select providers and then deal with those providers on your behalf for faults and changes. The circuits are contracted with the carrier.
Vendor liaison is a genuinely valuable and undersold part of this. Chasing a fibre provider through a fault is a real time cost that usually lands on whoever is least able to refuse it, and moving it is worth more than it looks on a service list.
When do we not need a network project?
When the environment is a single office, a handful of switches and a wireless network that people are not complaining about. Documentation and a configuration backup would still be worth a day of someone’s time, and beyond that you probably do not need us.
The point at which network work starts returning value is multiple sites, systems that share the network with business traffic, a wireless network carrying voice or scanners, or an estate nobody has documented. If none of those apply, spend the money elsewhere.