Project template ยท Markdown

Enterprise Network Design in Cisco Packet Tracer

A template for documenting a large-organisation Packet Tracer topology, addressing plan, configuration, and validation.

Project overview

Writing template: Replace each prompt with details from your own Packet Tracer design and test results.

Introduce the fictional or anonymized organisation, its requirements, and the scale of the network. Explain the assumptions behind the design without publishing sensitive real-world information.

Cisco networking logo

Requirements and assumptions

Requirement Design response How it will be verified
Multiple departments or VLANs [Describe the segmentation] [Describe the test]
Resilient connectivity [Describe redundancy choices] [Describe the failover check]
Centralized services [List services and locations] [Describe the reachability check]
Secure management [Describe management access controls] [Describe the verification]

Topology

[Insert an exported Packet Tracer topology screenshot. Keep the image under public/Images/projects/ and use a root-relative Markdown image path.]

Describe the sites, core/distribution/access layers, WAN links, edge devices, and important traffic paths.

Addressing and VLAN plan

Site VLAN Purpose Subnet Default gateway
[Site] [ID] [Department] [CIDR] [Address]
[Site] [ID] [Servers or services] [CIDR] [Address]
[Site] [ID] [Management] [CIDR] [Address]

Implementation

Switching and segmentation

[Document VLANs, trunks, spanning-tree choices, and any access-layer protections.]

Routing and WAN connectivity

[Document the routing design, route exchange, WAN addressing, and any failover behavior.]

Shared services and access controls

[Document services, access-control rules, and how management traffic is separated.]

# Add sanitized configuration excerpts or CLI output here.

Testing and results

Test Source and destination Expected result Actual result
Inter-VLAN connectivity [Hosts or networks] [Expected behavior] [Record result]
Restricted access [Source and protected resource] [Expected block/allow] [Record result]
WAN or link failover [Affected path] [Expected recovery] [Record result]

Design decisions and future improvements

  • Decision: [Choice and rationale]
  • Trade-off: [What the choice improves and what it costs]
  • Next step: [What you would expand or test next]

References

Back to all projects