Cisco Multi-Branch Network Design
Budget: $10 – $30 USD
I want a fault-tolerant, large-scale network built in Cisco Packet Tracer that links several branches exactly the way we will deploy it in production. You will start from a clean slate, analyse the requirements of each site, and hand back a complete Packet Tracer file ready to load on real equipment.
Because it is a multi-branch environment, I expect advanced configurations—dynamic routing (EIGRP/OSPF), VLAN segmentation, inter-VLAN routing, ACL-based security, DHCP, NAT, and any other features you deem necessary to keep traffic efficient and secure. High-availability links, troubleshooting toolsets, and clear IP addressing plans should also be part of the design.
When you deliver, I need:
• The finished .pkt topology with every device fully configured and verified.
• A Word document that walks me through the build step-by-step, includes all CLI commands, and explains the logic behind key design choices.
• A live hand-over session via AnyDesk so I can test fail-over scenarios, ask questions, and be certain everything behaves exactly as documented.
If additional complexity is required—for example more sites, specialised services, or integration with real hardware later on—we can expand the scope in follow-up milestones. Let me know what information you need from my side (addressing scheme, branch head-counts, specific hardware models, etc.) and we can get started right away.
Because it is a multi-branch environment, I expect advanced configurations—dynamic routing (EIGRP/OSPF), VLAN segmentation, inter-VLAN routing, ACL-based security, DHCP, NAT, and any other features you deem necessary to keep traffic efficient and secure. High-availability links, troubleshooting toolsets, and clear IP addressing plans should also be part of the design.
When you deliver, I need:
• The finished .pkt topology with every device fully configured and verified.
• A Word document that walks me through the build step-by-step, includes all CLI commands, and explains the logic behind key design choices.
• A live hand-over session via AnyDesk so I can test fail-over scenarios, ask questions, and be certain everything behaves exactly as documented.
If additional complexity is required—for example more sites, specialised services, or integration with real hardware later on—we can expand the scope in follow-up milestones. Let me know what information you need from my side (addressing scheme, branch head-counts, specific hardware models, etc.) and we can get started right away.