| Before purchase | Port count and growth | Count current wired endpoints, uplinks, and devices likely to be added during the planning period. | Allow spare ports for growth and maintenance. Check whether the switch needs copper, fiber, or a mix of port types. | Port inventory; growth forecast |
| Before purchase | Network capacity | Review access-port speeds, uplink speeds, switching capacity, and expected traffic between ports. | Match interface speeds to connected devices and upstream equipment. Confirm that uplinks will not become a bottleneck for expected traffic. | Traffic estimates; topology diagram |
| Before purchase | Power over Ethernet | Identify powered devices, their PoE standards and maximum power needs, plus the switch’s total PoE budget. | Check both per-port limits and the total power budget; include headroom for simultaneous device demand and future additions. | Device power list; PoE budget calculation |
| Before purchase | Layer 2 and Layer 3 features | Determine whether requirements include VLANs, link aggregation, spanning tree, routing, access control, or quality of service. | Select features based on the network design and staff expertise. Verify that required capabilities are supported in the intended operating mode. | Requirements checklist; design review |
| Before purchase | Resilience and environment | Assess power protection, cooling, rack space, operating conditions, and the impact of a switch outage. | Consider redundant power or links where downtime impact warrants them. Confirm rack depth, airflow clearance, and suitable power circuits. | Site survey; resilience plan |
| Installation | Configuration and security | Plan management addressing, administrator access, VLAN assignments, firmware, logging, and configuration backup. | Use unique administrator credentials, restrict management access, document approved settings, and back up the configuration after changes. | Configuration record; backup copy |
| Installation | Change and cutover plan | Identify dependencies, affected users, maintenance window, rollback steps, and tests for critical services. | Test configuration before cutover where practical. Record cable and port mappings, validate connectivity, and keep a documented rollback path. | Change plan; test checklist |
| Monitoring | Health and performance | Track device availability, port status, link errors, utilization, temperature, power supply status, and PoE consumption where available. | Set alert thresholds that reflect normal operating patterns. Review trends as well as individual alerts to identify capacity or reliability issues. | Monitoring dashboard; alert history |
| Monitoring | Logs and visibility | Check whether the switch can send event logs and expose operational metrics to the organization’s monitoring tools. | Centralize relevant logs, synchronize device time, and define who reviews alerts and how urgent events are escalated. | Logging configuration; escalation path |
| Ongoing support | Maintenance and firmware | Establish a process to review security advisories, assess updates, test changes, and schedule maintenance. | Keep a current inventory and configuration backup. Apply updates through a documented process that includes testing and rollback planning. | Maintenance calendar; update records |
| Ongoing support | Ownership and recovery | Assign responsibility for troubleshooting, access management, spare equipment, support escalation, and recovery documentation. | Document support contacts and response expectations. Periodically verify that a saved configuration can be restored and that recovery steps are current. | Support runbook; recovery test record |