01
A managed switch answers an operational need.
An unmanaged model can suit simple connectivity without settings. A managed model lets you define and observe behaviour within its feature set. Start with outcomes: separating guests, powering cameras, linking floors or finding a device’s port. The label “smart” is not a universal feature list.
Then name the network owner. An extensive interface without responsibility for configuration, updates and backups creates operational debt. The distributor compares documented references; the integrator turns requirements into architecture and tests. The client should know who owns the configuration and how to recover it, without putting secrets in quotations.
02
Compare each function with its evidence and purpose.
Scroll the table horizontally to compare all three columns.
| Need | Request | Keep separate |
|---|---|---|
| Ports and uplinks | Usable count, media, speeds and any shared ports. | Socket speed versus throughput to the service. |
| Segmentation | VLANs, port membership and rules between networks. | Creating a VLAN versus actually denying access. |
| Management | Local or controller access, backup and documented dependencies. | Cloud account versus network ownership. |
| Operations | Useful observations, updates, noise and supported environment. | Advertised feature versus delivered and tested configuration. |
03
Build a schedule for every proposal.
Count physical connections
List ID, room, role and required speed per endpoint. Add uplinks and known expansion. Check whether an optical cage is independent or shares resources with a copper socket. Reserve should answer named needs, not replace the inventory with a percentage.
Separate traffic and power
Identify simultaneous flows actually crossing the uplink and validate end-to-end capacity. Summed advertised port speeds are not measured traffic. Assess PoE types, per-port limits and shared budget separately; an available socket does not prove available power.
Write the intended permissions
Record who communicates with what: workstations to applications, cameras to recorder, guests to permitted access. State where rules are enforced and who maintains them. VLAN membership must be coherent along the path; it does not replace routing/filtering policy or a denied-access test.
Check the management model
Request the proposed version’s manual, enabled features and any licences. Document what continues if the controller or Internet is unavailable rather than assuming it. Plan named accounts, protected backups and return to the last approved configuration. Do not test an outage on an occupied network.
04
Twenty-four ports do not yet validate the network.
ILLUSTRATIVE EXAMPLE
Fictional office: 10 workstations, 4 cameras, 2 access points, 1 printer, 1 recorder and 1 dedicated copper uplink. Three sockets are reserved for identified expansion. No commercial reference is selected.
Separate occupied, reserved and free
The inventory occupies 19 ports. With 3 reserved, 22 are planned: 2 of 24 genuinely independent ports remain unallocated. The 5 unoccupied sockets are not all freely available. The six potentially PoE endpoints need a separate power check.
Test permission and denial
The authorised workstation reaches its service; the guest must not reach management. If both do, the scenario fails despite different VLAN names. Correct the policy and enforcement rather than removing the control to pass the test.
Hand over an operable configuration
The record maps sockets to ports and roles, states the approved version and tests, and names the backup custodian. Review recovery with the owner; finding a file does not establish that restoration was tested.
Documentary example: no scan, VLAN change or real outage. It establishes no guaranteed throughput or certified security level.
05
Accept behaviour, not only hardware.
Port correspondence
Check labels, media and observed speeds, then the intended service on authorised test endpoints. Record differences and untested devices. Link-up does not prove recording or a completed call.
Management and separation
Verify authorised management and rejection of excluded profiles within a written scope. Advanced features such as aggregation or multicast handling need a documented purpose and configuration, not random activation because a datasheet lists them.
Ongoing operation
Deliver inventory, versions, licence dependencies and results. Name alert recipients, update responsibility and intervention conditions. Transfer passwords through an agreed protected channel, never in a shared equipment list.
06
Request genuinely comparable proposals.
Send the port schedule, concurrent uses, PoE needs and management conditions. Tie every required feature to a reference/version and make exclusions visible. Include accessories, optics, mounting and power. Inovexia prepares documented selection and quotation; network policy and acceptance remain separate deliverables to agree with the integrator.
07
Distinctions that prevent a poor purchase.
Does managed mean router or firewall?
No. Some functions may coexist on a model, but verify each explicitly. Locate routing, filtering and management rather than inferring them from “managed”.
Is a VLAN enough to isolate guests?
It is one part. Membership, permitted flows, routing and rules must match the requirement. Test allowed and denied access; different network names do not prove isolation.
Do all switches require cloud management?
No. Check the model’s management mode, dependencies and offline functions. Establish account ownership and transfer procedure; do not assume offline availability.
Do two links always double one transfer’s speed?
No. Aggregation, its modes and flow distribution depend on equipment and configuration. Specify capacity or continuity needs and request a representative test, not a marketing sum.
Can another site’s configuration be reused?
Not without review. Identities, VLANs, permissions, devices and paths differ. A starting template is not an approved configuration. Authorise, adapt, back up and test any reuse with recovery planned.
Technical sources
External reading references. These documents explain principles; they do not certify catalogue products or their combination.
- How does a switch work?Cisco · Sources consulted on
- Configure Port to Virtual Local Area Network (VLAN) Settings on a SwitchCisco · Sources consulted on
- PoE Availability and ModesUbiquiti · Sources consulted on