Tag Archives: CCDA


This starts my foray into the CCDA. I will try to keep the CCDA notes blog posts to a specific topic per post. If you see any mistakes, missed subject matter, or just wish to berate my note taking skills then feel free to leave a comment.


1) Business objectives. Identify technologies and develop a strategy.
2) Identify customer requirements.
    a) Speak with all managers.
    b) Follow these steps:
     Step 1. Identify network applications and services.
     Step 2. Define organizational goals.
     Step 3. Define organizational constraints.
     Step 4. Define technical goals.
     Step 5. Define technical constraints.

1) Characterize and asses the network to develop a project plan.
2) Information gathering.
    Step 1. Identify and gather all existing documentation.
    Step 2. Audit the network.
    Step 3. Perform traffic analysis.
3) Information to gather:
    a) Device list
    b) Hardware models
    c) Software versions
    d) Configs
    e) Auditing tools output
    f) Interface speeds
    g) Link, cpu, and memory utilization
    h) WAN technologies

1) Top Down Approach
    a) Start with apps and work your way down to the network infrastructure.
    b) Accurately incorporates the business drivers.
    c) Disadvantage is that it is time-consuming.
2) Bottom Up Approach
    a) Based on previous experience.
    b) Allows for quick solutions.
    c) Might make for inappropriate solutions.
    d) Often misses the organizational goals.
3) Pilots and prototypes
    a) Prototype – A subset of a full network. These networks are generally isolated from production network.
    b) Pilot – A live location for testing on the actual network. Allows the discovery of any real issues.
4) A design document generally includes:
    a) Introduction
    b) Design requirements
    c) Existing network infrastructure
    d) Design
    e) PoC
    f) Implementation plan
    g) Appendices

1) Follow the project plan and design document.
2) Each step should include:
    a) Description
    b) Implementation guidelines
    c) Estimated time to complete
    d) Rollback steps
    e) Reference information

1) Network management
2) Network monitoring
3) Routine maintenance
4) Upgrades
5) Performance management
6) Network fault detection and correction

1) Be proactive instead of reactive
2) This may lead back to the Prepare phase and start the process all over.


Quick Update

Have not posted in a while so wanted to give a quick update. I am about to finish up my “CCNP memory refresh”. I am half way through my final book and should finish it off in the next week or so.

The last book I am reading is Network Warrior Second Edition. This book is really good. I had read the first edition and forgot how much I like Gary Donahue’s writing style which is informative and funny at just the right times.

My big plans after completing this refresh are lining up perfectly. The CCDA books will be coming out during the month of June, just in time for me to start up my CCDA/DP path. Plans are to have it done by end of year and then 2012 will be my start up that big mountain know as the CCIE. I do plan to try, notice the word try there, to blog more on the topics I go over for the CCDA/DP studies so stay tuned for some boring posts on design and such.

See ya around!