CCDP Certification Studying Suggestions

These files/documents are recommended studying material that I have found and gathered into a single location. This will be a live document, and updated with any new material found. This is for the 300-320 certification. As always, do your own research as some of this may eventually become out of date, and may be outside of the scope of the CCDP Arch certification and more driven towards CCDE.

Videos
- Cisco Learning Network - Practical Network Design Fundamentals
- CBT Nuggets - Even though it says that it is 642-784, the bottom section 3.0 has been updated to reflect the most recent changes

Books
- Designing for Cisco Network Service Architectures (ARCH) Foundation Learning Guide: CCDP ARCH 300-320 (4th Edition) - This can be purchased from Amazon or Cisco Press
- CCDE Study Guide - This can be purchased from Amazon/Cisco Press

Supplementary Materials

Campus

- Enterprise Campus 3.0 Architecture Overview
- HA Campus Network Design
- Campus Wired LAN Technology Design Guide
- Campus Network for HA Design Guide
- Campus Design Summary
- HA Campus Recovery Analysis

Data Center

- VMDC DCI 1.0 Design Guide
- Cisco OTV Technology Introduction and Deployment Considerations
- DC Access Layer Design
- OTV Best Practices Guide
- DC OTV White Paper
- DC Design Summary

Internet Edge, WAN and Security

- IE Design Summary
- Intelligent WAN & WAN Design Summary
- MPLS WAN Technology Design Guide
- IPSec VPN WAN Design Overview
- Enterprise Security Baseline for LAN, Wireless LAN and WAN

Comments

Fortigate to USG B2B

Building Site-to-Site B2B from Unifi USG to Fortigate (500D or other models) Fortigate Configuration 1. Build a New VPN Tunnel using Custom VPN Tunnel (No Template) 2. Under Network, point to the Public Side IP of the USG (Public IP, not WAN interface) 3. Leave everything else default (NAT-T Enabled, DPD Disabled..ect) 4. Authentication, use PSK and IKEv1 with Main 5. Phase 1 Purposal, set algorithms to AES128 and SHA1, with DH 14. 6. Phase 2 Purposal, set Local Address and Remote address to 0.0.0.0/0.0.0.0 and 0.0.0.0/0.0.0.0 respectively. 7. Set Encryption to AES128/Sha1, Replay Detection and PFS enabled, along with DH14. Enable Autokey Keep Alive, and Auto-Negotiate, and save changes. 8. Build a Static Route pointing to the Far-End Destination/Segment you want to reach. 9. Build a Policy Stating which Segments can hit the Far-End Destination/B2B USG Configuration 1. This is assuming that USG is already registered to the Unifi Controller. 2. Go t

How to setup a Host-Check for Fortigate SSL VPN

This document outlines how to setup a host-check for a Fortigate SSL VPN (Web only): config vpn ssl web portal edit "portalname" set web-mode enable set host-check custom set host-check-policy "Microsoft-Windows-Firewall" set os-check-enable set ip-pools "PoolName" set split-tunneling disable set page-layout double-column set theme orange config os-check-list "windows-7" set action check-up-to-date set latest-patch-level 1 end config vpn ssl web host-check-software edit "Microsoft-Windows-Firewall" config check-item-list edit 1 set target "HKLM\\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile:EnableFirewall==1" set type registry next edit 2 set target "HKLM\\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile:EnableFirewall==1" set type registry next edit 3 set target "HKLM\\SYSTEM\\CurrentControlSet\\S

Implementing 802.1X - Windows 2012R2 + Cisco 4500 Switches

Implementing 802.1X Using Windows Server 2012R2 & Cisco 4500 Series Switches Overview: This document is to outline how the configuration between Windows Server 2012 R2’s NPS Services and Cisco 4500 Series switches has been implemented. High Level Diagram: Requirements: Windows Server 2012 R2 with NPS Server installed Windows Server 2012 R2 with CA Services Windows AD Environment Cisco 4500 Series Switches Windows 7-10 Clients to connect NPS Configuration: 1. This assumes the above requirement that the NPS Service has already been installed on Windows Server 2012 R2 2. Disable all existing Policies under Connection Request Policies and Network Policies as you will be making your own, except one that states “Catch All” with the below parameters: 3. You will then need to add in a new Radius Client to have Policies built around. Friendly Name will be used going forward for the Policies for referencing the document. 4. Once completed, re

ElderUsr's Blog

Search This Blog