NETWORK SEGMENTATION

Enterprise VLAN Setup and Network Segmentation

We separate user, server, guest, camera and production networks by purpose. Before the cutover we map DNS, DHCP, printer, phone and critical application access, and test that these services work with the new rules. In facilities with production machines and an automation network, factory network segmentation is planned separately according to site conditions.

The right boundaries, a more manageable network

The basic question in segmentation is which group reaches which service on which port.

SERVICE SCOPE / 01

We split a single flat network into manageable segments

In a network growing in a single broadcast domain, broadcast traffic increases, access permissions sprawl and troubleshooting takes longer. We design segmentation together with Layer 2 separation, Layer 3 routing and security policy.

01

Boundaries

VLAN and subnet mapping

02

Access

ACL/firewall rule matrix

03

Routing

SVI, gateway and route design

04

Operation

Trunks, DHCP relay and documentation

TECHNICAL APPROACH / 02

VLANs separate, routing connects, rules control

Every technical decision has a reason: shrinking the broadcast domain, limiting the spread of an attack, moving traffic to a backup path during a failure and keeping the structure manageable.

VLAN segmentation

The 802.1Q tag contains a 12-bit VLAN ID field to identify the VLAN. The number of active VLANs a device supports depends on the model and software version. A VLAN separates Layer 2 broadcast domains; every VLAN should have a security or management reason.

Inter-VLAN routing

In most environments, inter-VLAN routing is done with SVI interfaces on the core switch. In a small environment, router-on-a-stick may be enough. A single trunk can create a capacity limit or a single point of failure, depending on the traffic carried and the link speed.

Trunk and access ports

Trunk ports between switches carry only the required VLANs. The native VLAN and trunk settings are set according to both ends, the platform and the topology, and must be the same at both ends. Endpoint ports are mostly single-VLAN; ports with voice/data separation, such as an IP phone with a computer behind it, are defined separately.

ACLs and security

Permissions between networks are enforced by an ACL or firewall policy at the routing point. Switch ACLs are for simple stateless filters; traffic that needs stateful inspection passes through the firewall. Required management access is defined with source, destination, purpose and owner. To set the inter-segment access policy from a security perspective, you can use the enterprise network security and access policies work.

Redundancy

With VRRP, two devices share a single virtual gateway address; when the active device becomes unreachable, the other takes over. Dynamic routing protocols such as OSPF learn backup paths between sites.

Documentation

The VLAN/IP table, rule matrix, port map and configuration backups are handed over.

ENGINEERING APPROACH / 03

We separate network traffic according to business needs

Segmentation is done on a live network. Every step is written down in advance, tested and applied in a way that can be rolled back. Independent segments such as management and guest are separated first; user groups are moved in stages.

01

Segment matrix

The services, protocols and management access each segment will talk to are put in writing.

02

Routing policy

Inter-VLAN routing, firewall traversal and ACL order are verified together with their dependencies.

03

Migration plan

DHCP relay, DNS, printers, IP phones and industrial devices are tested one by one on the new network.

EXAMPLE PLAN / 04

Example VLAN and access plan

The numbers are examples; the real plan comes from your device groups and workflows. The rule logic: block by default, define the access that is needed.

VLANGroupAccess rule
VLAN 10UsersTo servers only on the required ports
VLAN 20IP phonesVoice server and SIP
VLAN 30IP cameras and NVRRecording server only; no internet access
VLAN 40GuestInternet only; no access to the internal network
VLAN 99Network device managementIT administrator workstations only
CONCRETE DELIVERABLES / 05

What will you have at the end of the segmentation work?

A VLAN and IP plan, inter-VLAN access rules, the routing structure and post-cutover verification records. A written answer to the question “who can reach what?”

A documented, verifiable result

01

VLAN/subnet and gateway plan

02

Source-destination access rule matrix

03

Trunk/access port profiles

04

Per-segment connectivity and security tests

FREQUENTLY ASKED QUESTIONS / 06

Let’s clarify a detail

If you have a question specific to your network, write to us; we’ll look at your current setup and give you a clear answer.

01

Does a VLAN provide security on its own?

No. A VLAN only separates Layer 2 broadcast domains. Security between segments is provided by the ACL or firewall policy at the routing point.

02

Can we split our existing flat network into VLANs without interrupting work?

It can be done in stages. Independent segments such as management and guest are separated first, then cameras and phones are moved. Each stage has a rollback plan; steps that carry an outage risk are done in a maintenance window. There may be short interruptions during the cutover.

03

How many VLANs are needed?

As many as needed. Every VLAN should have a security or management reason. Unnecessary segmentation inflates the number of rules and makes management harder.

04

Should inter-VLAN routing be done by the switch or the firewall?

High-volume, trusted internal traffic is routed on the core switch; traffic that needs inspection is routed on the firewall. The segmentation policy determines which traffic goes where.

ERETEK NETWORK

Let’s divide your network into secure segments

Let’s list your current device and user groups, and prepare the VLAN, IP and access rule plan on that basis together.