Wise IT, IT done wisely
Client support Let’s talk

Network review guide

Enterprise and carrier network assessment checklist

A useful network assessment connects diagrams and configurations to the services people depend on. This checklist covers enterprise sites, data centers and provider networks without assuming they share the same design.

By

Start with services and boundaries

Identify the business or customer services in scope, the locations they cross and the teams that own them. Record availability targets, maintenance restrictions and the effect of delay, packet loss or a complete outage.

Define the edge of the assessment. It may stop at a campus firewall, include cloud networks and wide-area circuits, or extend through a carrier backbone and peering edge. Document responsibility at every handoff between the business, a colocation facility, an internet provider, a managed service and an application team.

1. Inventory physical and logical components

  • Sites, racks, power feeds, cabling paths and environmental dependencies
  • Routers, switches, firewalls, wireless controllers, access points and appliances
  • Hardware models, software versions, support status and spare strategy
  • Internet, private WAN, broadband, Metro Ethernet, wavelength, dark fiber and cellular circuits
  • IP address space, autonomous system numbers, VLANs, VRFs and cloud networks
  • DNS, DHCP, NTP, authentication, certificates and management services

Reconcile diagrams with configurations, discovery data, contracts and a physical sample. Record unknown devices and undocumented connections as findings.

2. Trace topology, routing and traffic paths

Follow several important flows from source to destination. Include normal paths, backup paths, security inspection and any translation or tunneling. Check whether the written design matches active forwarding.

  • Layer 2 boundaries, spanning tree, link aggregation and failure domains
  • Static routing and protocols such as BGP, OSPF and IS-IS
  • MPLS, EVPN and VXLAN services where they are used
  • SD-WAN policy, VPNs and cloud connectivity
  • Route filtering, summarization, redistribution and default routes
  • Quality of service for voice, video and other time-sensitive traffic
  • Multicast design when applications require it

For internet-facing BGP, review prefix filters, maximum-prefix controls, session protection and the organization's route-registration and RPKI practices where applicable. Carrier networks should also document customer route policy and escalation ownership.

3. Measure capacity and service quality

Interface speed alone does not describe user experience. Review utilization at useful intervals and during known business peaks. Look at errors, discards, retransmissions, latency, jitter and packet loss where the tools make those measurements possible.

Compare circuit billing and committed rates with actual configuration. Check uplinks, firewall throughput, wireless airtime and oversubscribed paths. Flow records such as NetFlow or IPFIX can help explain who uses the capacity, provided collection and retention are approved.

Record the baseline and the collection period. One quiet hour should not be used to size a seasonal service.

4. Review segmentation and administrative security

Map trust zones and the policies between them. Common separations include users, servers, management, guest wireless, voice, cameras, building systems and customer environments. Confirm that firewall and access-control rules have owners and a review process.

  • Dedicated administrative accounts and multi-factor authentication where supported
  • Restricted management sources and protected out-of-band access
  • Encrypted management protocols and current certificates
  • Central logs, configuration backups and change records
  • Vendor access that is approved, limited and removed when no longer needed
  • Control-plane protections suited to the platform and role

Test a sample of rules against current traffic and business need. A clean rule name does not prove that the path is still required.

5. Test resiliency with the full dependency chain

Redundant equipment can share a power source, fiber path, upstream provider or control service. Draw the failure domains and identify components whose loss affects both the primary and alternate path.

Review convergence timers and state synchronization, then test a controlled failure where the business permits it. Observe application behavior, voice quality, routing changes, alerts and the time required to recover. Document manual steps and the authority needed to perform them.

Include DNS, identity, monitoring and remote access in the scenario. A backup circuit has limited value if the team cannot administer the environment during the outage.

6. Inspect monitoring and operating practice

Review what the team can see and how it responds. SNMP, streaming telemetry, syslog, flow data and synthetic tests answer different questions. Confirm time synchronization, alert routing, retention and access to the tools during an incident.

  • Who owns each device, circuit, address block and provider relationship?
  • How are configuration changes reviewed, backed up and verified?
  • Can the team find circuit IDs and escalation contacts quickly?
  • Are recurring alerts investigated or repeatedly cleared?
  • Do lifecycle and capacity forecasts lead to funded decisions?
  • Can another qualified person use the diagrams and runbooks?

Turn the assessment into owned work

The final package should include the verified scope, current diagrams, material evidence, findings, dependencies and a prioritized improvement plan. Separate an observed condition from its likely effect and from the recommended change. Assign a decision owner and a way to verify each completed item.

Wise IT provides enterprise and carrier network consulting for routing, switching, wireless, WAN, service-provider and data-center environments. A broader IT environment and ownership review can place network findings alongside cloud, recovery, security and vendor responsibilities.

Evidence before redesign

Trace the service, test assumptions and assign the work.

A network assessment should leave the next engineer with usable diagrams, current evidence and clear decisions.

Review Wise IT's technical capabilities

Need an independent network review?

Share the sites, services and recurring problems that need attention.

Discuss a network assessment