SWITCHING AND ROUTING

Enterprise Switch and Router Installation

When installing switches and routers, we decide in advance which port connects where, which VLANs it carries and how management access will be provided. After the cutover, we test endpoint devices, backup links and management access.

Tested installation and port plan

We complete the installation with connectivity and redundancy tests after the cutover.

SERVICE SCOPE / 01

What every installation covers as standard

During installation we verify uplinks, VLAN policies, loop protection, management access and the rollback plan together.

01

Uplink

LACP, port-channel and capacity based on need

02

Layer 2

802.1Q, STP/RSTP and port profiles

03

Layer 3

Static/dynamic routing and gateway architecture

04

Operation

Configuration backup and port documentation

TECHNICAL SCOPE / 02

From Layer 2 to Layer 3

The topics we cover during installation are below.

Switching

Loops are prevented with RSTP or MSTP. We choose the root bridge location based on the Layer 2 topology; on edge ports we use the edge port and BPDU protection settings the platform supports. Uplinks are built with LACP (802.1AX). If the members of a LACP group are to be spread across different physical switches, these two devices must form a single logical system like a stack or support a suitable multi-chassis link (MLAG) technology.

Routing

In most environments, inter-VLAN routing is done with SVI interfaces on the core switch. If there are multiple sites or backup paths, dynamic routing such as OSPF is used, and VRRP or HSRP for gateway redundancy. For production panels and field switches, a design suited to industrial conditions is done separately within industrial Ethernet and factory network design.

Security

DHCP Snooping blocks DHCP server responses coming from untrusted ports. Dynamic ARP Inspection (DAI) compares ARP packets with the binding information kept by DHCP Snooping; so it relies on trusted binding entries and correct trusted port settings. For devices using static IPs, a separate entry or ARP access list is defined. Unused ports and unencrypted protocols such as Telnet are disabled; administrator access is tied to central authentication with RADIUS or TACACS+ where possible.

PoE and capacity

The PoE budget for IP phones, cameras and access points is calculated before choosing devices (802.3af, 802.3at, 802.3bt). Uplink capacity is assessed relative to the total speed of the access ports (oversubscription).

ENGINEERING APPROACH / 03

What is settled before installation

Most decisions are made before going on site: devices are preconfigured, the port map is prepared and the cutover is done with a rollback plan. We set the expected downtime based on the time measured in a pilot cutover and on dependencies.

01

Ports and physical connections

SFP/DAC/fiber compatibility, PoE budget, uplink speed and port roles are settled in the design.

02

Controlled access

The management VLAN, ACLs, secure remote access and the required device management services are configured.

03

Failure scenarios

Uplink failure, failover, the STP root location and, if any, gateway redundancy are checked.

EXISTING DEVICES / 04

Not every project needs new hardware

In some networks the existing devices are sufficient and improvement can be achieved through configuration. We can review the software versions, licenses and configurations of existing switches and routers and reorganize them.

What we do on existing devices

  • Identifying out-of-support (EoL/EoS) devices
  • Updating software versions according to security bulletins
  • Configuration cleanup: unused VLANs, old users, open services
  • Rebuilding port and VLAN documentation
CONCRETE DELIVERABLES / 05

What will you have at the end of the installation?

Backed-up, standardized device configurations, a port and IP plan, and commissioning test records. Every later change starts from a clean point.

A documented, verifiable result

01

Port/VLAN mapping table

02

Per-device configuration and backup

03

Uplink, routing and failover test report

04

Management access and change log

FREQUENTLY ASKED QUESTIONS / 06

Let’s clarify a detail

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

01

Can the installation be done outside working hours?

Yes. Once the scope of the change, dependencies and the rollback plan are clear, cutovers that require downtime are scheduled in a suitable maintenance window. The expected downtime is based on the time measured in a pilot cutover and on dependencies.

02

Do devices from different vendors work on the same network?

In most cases, yes. 802.1Q VLANs, LACP, RSTP/MSTP, OSPF and LLDP are standard protocols. Interoperability depends on device model, software version and configuration; it is tested before the cutover. If vendor-specific protocols have been used, moving to their standard equivalents is planned.

03

Are the configuration files handed over to us?

Yes. Configuration backups, the method for storing management access details, the port map and the topology diagram are handed over at the end of the project.

ERETEK NETWORK

Let’s talk about installing and renewing your network devices

Share your device list or current topology; let’s work out the right configuration and cutover plan together.