Difference between revisions of "CCDA - en"

From Teknologisk videncenter
Jump to: navigation, search
m (→‎SONA Lag)
m (→‎Sections in a Design dokument)
 
(23 intermediate revisions by the same user not shown)
Line 12: Line 12:
 
#'''Integrated Applications:'''
 
#'''Integrated Applications:'''
  
 +
=Reading plan=
 +
See fronter Network Semester 3
 +
<!--
 +
{|border=1 ;style="margin: 0 auto; text-align: center;cellpadding="5" cellspacing="0"
 +
|+ Reading plan
 +
|- bgcolor=lightgrey
 +
! Date !! Day !! Subject
 +
|-
 +
| Sep. 10. || Tuesday || Chapter 1:  [[/Network design methodology | Network design methodology]]  and chapter 2: [[/Network Structure models | Network Structure models]]
 +
|-
 +
| Sep. 17. || Tuesday || Chapter 3:  [[/Enterprise LAN design | Enterprise LAN design]] 
 +
|-
 +
| Sep. 18. || Wednesday || Chapter 4: [[CCDA/Wireless_LAN_design|Wireless_LAN_design]] Exercise 1 part 1: [[/Viborg Kommune|Viborg Kommune]]
 +
|-
 +
| Oct. 9. || Wednesday || Chapter 5:  [[CCDA/WAN Technologies WAN | WAN Technologies]]  Chapter 6:  [[CCDA/WAN design | WAN design]]
 +
|-
 +
| Oct. 11. || Friday || Chapter 7:  [[CCDA/Internet Protocol version 4 | Internet Protocol version 4]]  Chapter 8:  [[CCDA/Internet Protocol version 6 | Internet Protocol version 6]] 
 +
 +
 +
  [[CCDA/Case maj 2012|Case]]  - Kapitel 9:  [[CCDA/Routing Protocol Selection Criteria | Routing Protocol Selection Criteria]]
 +
|-
 +
| 14. maj || Mandag ||    [[CCDA/Case maj 2012|Case]]  - Kapitel 10:  [[CCDA/RIP and EIGRP Characteristics and Design | RIP and EIGRP Characteristics and Design]] og Kapitel 11:  [[CCDA/OSPF and IS-IS | OSPF and IS-IS]] 
 +
|-
 +
| 15. maj || Tirsdag ||  [[CCDA/Case maj 2012|Case]]  - Kapitel 12:    [[CCDA/Border Gateway Protocol, Route manipulation and IP Multicast | Border Gateway Protocol, Route manipulation and IP Multicast]] og Kapitel 13:  [[CCDA/Security Management | Security Management]]
 +
|-
 +
| 16. maj || Onsdag ||  [[CCDA/Case maj 2012|Case]]  - Kapitel 14:    [[CCDA/Security Technologies and design | Security Technologies and design]]  og Kapitel 15:  [[CCDA/Traditional Voice Architectures and IP Telephony design | Traditional Voice Architectures and IP Telephony design]]
 +
|-
 +
| 21. maj || Mandag ||  [[CCDA/Case maj 2012|Case]]  - Kapitel 16: [[CCDA/Network Management protocols | Network Management protocols]]   
 +
|-
 +
| 22. maj || Tirsdag || Afslutning og overhøring gruppevis
 +
 +
|-
 +
|}
 +
-->
 +
 +
=Materials=
 
== The Book ==
 
== The Book ==
 
'''CCDA''' Official Exam Certification Guide
 
'''CCDA''' Official Exam Certification Guide
 
*ISBN: 978-1-58720-177-6
 
*ISBN: 978-1-58720-177-6
 
=== Part I - General Network Design ===
 
=== Part I - General Network Design ===
−
*Chapter 1: [[CCDA/Network design methodology | Network design methodology]]
+
*Chapter 1: [[/Network design methodology | Network design methodology]]
−
*Chapter 2: [[CCDA/Network Structure models | Network Structure models]]
+
*Chapter 2: [[/Network Structure models | Network Structure models]]
  
 
=== Part II - LAN and WAN design ===
 
=== Part II - LAN and WAN design ===
−
*Chapter 3: [[CCDA/Enterprise LAN design | Enterprise LAN design]]
+
*Chapter 3: [[/Enterprise LAN design | Enterprise LAN design]]
 
*Chapter 4: [[CCDA/Wireless LAN design | Wireless LAN design]]
 
*Chapter 4: [[CCDA/Wireless LAN design | Wireless LAN design]]
−
*Chapter 5: [[CCDA/WAN Technologies WAN | Technologies]]
+
*Chapter 5: [[/WAN Technologies WAN | Technologies]]
−
*Chapter 6: [[CCDA/WAN design | WAN design]]
+
*Chapter 6: [[/WAN design | WAN design]]
 +
 
 
=== Part III - The Internet Protocol and Routing Protocols ===
 
=== Part III - The Internet Protocol and Routing Protocols ===
−
*Chapter 7: [[CCDA/Internet Protocol version 4 | Internet Protocol version 4]]
+
*Chapter 7: [[/Internet Protocol version 4 | Internet Protocol version 4]]
−
*Chapter 8: [[CCDA/Internet Protocol version 6 | Internet Protocol version 6]]
+
*Chapter 8: [[/Internet Protocol version 6 | Internet Protocol version 6]]
−
*Chapter 9: [[CCDA/Routing Protocol Selection Criteria | Routing Protocol Selection Criteria]]
+
*Chapter 9: [[/Routing Protocol Selection Criteria | Routing Protocol Selection Criteria]]
−
*Chapter 10: [[CCDA/RIP and EIGRP Characteristics and Design | RIP and EIGRP Characteristics and Design]]
+
*Chapter 10: [[/RIP and EIGRP Characteristics and Design | RIP and EIGRP Characteristics and Design]]
−
*Chapter 11: [[CCDA/OSPF and IS-IS | OSPF and IS-IS]]
+
*Chapter 11: [[/OSPF and IS-IS | OSPF and IS-IS]]
−
*Chapter 12: [[CCDA/Border Gateway Protocol, Route manipulation and IP Multicast | Border Gateway Protocol, Route manipulation and IP Multicast]]
+
*Chapter 12: [[/Border Gateway Protocol, Route manipulation and IP Multicast | Border Gateway Protocol, Route manipulation and IP Multicast]]
 
=== Part IV - Security, Convergence and Network Management ===
 
=== Part IV - Security, Convergence and Network Management ===
−
*Chapter 13: [[CCDA/Security Management | Security Management]]
+
*Chapter 13: [[/Security Management | Security Management]]
−
*Chapter 14: [[CCDA/Security Technologies and design | Security Technologies and design]]
+
*Chapter 14: [[/Security Technologies and design | Security Technologies and design]]
−
*Chapter 15: [[CCDA/Traditional Voice Architectures and IP Telephony design | Traditional Voice Architectures and IP Telephony design]]
+
*Chapter 15: [[/Traditional Voice Architectures and IP Telephony design | Traditional Voice Architectures and IP Telephony design]]
−
*Chapter 16: [[CCDA/Network Management protocols | Network Management protocols]]
+
*Chapter 16: [[/Network Management protocols | Network Management protocols]]
  
 
=== Part V - Comprehensive Scenarios ===
 
=== Part V - Comprehensive Scenarios ===
−
*Chapter 17: [[CCDA/Comprehensive Scenarios | Comprehensive Scenarios]]
+
*Chapter 17: [[/Comprehensive Scenarios | Comprehensive Scenarios]]
 +
 
 
= Summary =
 
= Summary =
 
== IIN ==
 
== IIN ==
Line 57: Line 95:
 
|}
 
|}
  
−
== SONA Lag ==
+
== SONA Layer ==
 
{| class="wikitable sortable" cellspacing="1" cellpadding="1" summary="Cisco" border="1"
 
{| class="wikitable sortable" cellspacing="1" cellpadding="1" summary="Cisco" border="1"
−
|+ SONA lag (Service-Oriented Network Architecure)
+
|+ SONA layer (Service-Oriented Network Architecure)
 
|- bgcolor="#d3d3d3"
 
|- bgcolor="#d3d3d3"
 
! scope="col" | SONA lag
 
! scope="col" | SONA lag
Line 78: Line 116:
 
! scope="col" | Description  
 
! scope="col" | Description  
 
|-
 
|-
−
| Identity Services || Inkluderer [[AAA]], [[NAC]] og [[NBAR]]
+
| Identity Services || Including [[AAA]], [[NAC]] og [[NBAR]]
 
|-
 
|-
−
| Mobility Services || Adgang uanset hvor man er
+
| Mobility Services || Access to network services regardless of physical location
 
|-
 
|-
−
| Storage Services || Storage af kritiske data
+
| Storage Services || Storage of critical data
 
|-
 
|-
−
| Compute Services || Forbedrer Compute ressourcer. (Virtualisering)
+
| Compute Services || Enhancing compute resources (Virtualization)
 
|-
 
|-
−
| Security Services || Sikkerhed for alle ressourcer
+
| Security Services || Security of all resources
 
|-
 
|-
−
| Voice and collaboration Services || Fælles services og programmer
+
| Voice and collaboration Services || Shared services and programs
 
|-
 
|-
 
|}
 
|}
 +
 
== PPDIOO ==
 
== PPDIOO ==
 
{| class="wikitable sortable" cellspacing="1" cellpadding="1" summary="Cisco" border="1"
 
{| class="wikitable sortable" cellspacing="1" cellpadding="1" summary="Cisco" border="1"
−
|+ [[Network_design_methodology#PPDIOO|PPDIOO]] Netværk livscyklus faser (Prepare, Plan, Design, Implement, Operate og Optimize)
+
|+ [[Network_design_methodology#PPDIOO|PPDIOO]] Network live-cycle phases (Prepare, Plan, Design, Implement, Operate og Optimize)
 
|- bgcolor="#d3d3d3"
 
|- bgcolor="#d3d3d3"
 
! scope="col" | PPDIOO aktivitet
 
! scope="col" | PPDIOO aktivitet
 
! scope="col" | Description  
 
! scope="col" | Description  
 
|-
 
|-
−
| Prepare ||  Hvilke forretningskrav har virksomheden. Identificer teknologier (voice etc) som skal anvendes, og udarbejd en netværksstrategi.
+
| Prepare ||  DThe Prepare phase establishes organization and business requirements, develops a network
 +
strategy, and proposes a high-level architecture to support the strategy. Technologies that support
 +
the architecture are identified. This phase creates a business case to establish a financial
 +
justification for a network strategy.
 
|-
 
|-
−
| Plan || Identificer netværkskravene ved at sammenligne det fysiske netværk med forretningskravene fra Preparefasen. Udarbejd en projekt plan.
+
| Plan || The Plan phase identifies the network requirements by characterizing and assessing the network,
 +
performing a gap analysis against best-practice architectures, and looking at the operational
 +
environment. A project plan is developed to manage the tasks, responsible parties, milestones, and
 +
resources to do the design and implementation. This project plan is followed during all phases of
 +
the cycle.
 
|-
 
|-
−
| Design || Design netværket ud fra resultater fra ''Prepare'' og ''Plan'' faserne. Nøgleord: High Availability, Security, Scalability og Performance.
+
| Design ||The network design is developed based on the technical and business requirements obtained from
 +
the previous phases. The network design provides high availability, reliability, security, scalability,  
 +
and performance. The design includes network diagrams and an equipment list. The project plan
 +
is updated with more granular information for implementation. After the Design phase is
 +
approved, the Implement phase begins.
 
|-
 
|-
−
| Implement || Installer og konfigurer det nye udstyr.
+
| Implement || New equipment is installed and configured in the Implement phase. New devices replace or
 +
augment the existing infrastructure. The project plan is followed during this phase. Planned
 +
network changes should be communicated in change control meetings, with necessary approvals
 +
to proceed. Each step in the implementation should includes a description, detailed
 +
implementation guidelines, estimated time to implement, rollback steps in case of a failure, and
 +
any additional reference information. As changes are implemented they are also tested before
 +
moving to the Operate phase.
 
|-
 
|-
−
| Operate || Daglig netværksdrift.  
+
| Operate || The Operate phase maintains the network’s day-to-day operational health. Operations include
 +
managing and monitoring network components, routing maintenance, managing upgrades,
 +
managing performance, and identifying and correcting network faults. This phase is the design’s
 +
final test. During operation, network management stations should monitor the network’s general
 +
health and generate traps when certain thresholds are reached.
 
|-
 
|-
−
| Optimize ||  Proaktivt Network Management. Modificer design løbende.
+
| Optimize ||  The Optimize phase involves proactive network management by identifying and resolving issues
 +
before they affect the network. The Optimize phase may create a modified network design if too
 +
many network problems arise, to improve performance issues, or to resolve application issues. The
 +
requirement for a modified network design leads to the network life cycle beginning.
 
|-
 
|-
 
|}
 
|}
−
== Top-down eller Bottom-up design ==
+
 
 +
== Top-down or Bottom-up design ==
 
=== Top-down design ===
 
=== Top-down design ===
−
Tager hensyn til virksomhedens behov og giver stort overblik. Designet tilpasses nuværende og fremtidige behov.
+
 
−
*'''Ulemper:'''
+
Incorporates the organization’s requirements. Provides the big picture. The design meets current and future requirements.
−
**Tidskrævende
+
*'''Disadvantages:'''
−
**Dyrere ''nu-og-her''.
+
**Time demanding
 +
**Expensive ''short term''.
 
=== Bottom-up design ===
 
=== Bottom-up design ===
−
Designet er baseret på erfaringer fra netværket og giver en hurtig løsning på behovet nu og her.
+
The design is based on previous
−
*'''Ulemper:'''  
+
experience and allows for a quick
−
**Uhensigtsmæssigt design, tab af overblik.
+
solution.
−
**Virksomhedens fremtidige behov dækkes ikke.
+
*'''Disadvantages:'''  
−
== Sektioner i et Design dokument ==
+
**May result in inappropriate design.  
 +
**Organizational requirements are not included.
 +
 
 +
== Sections in a Design dokument ==
 
{| class="wikitable sortable" cellspacing="1" cellpadding="1" summary="Cisco" border="1"
 
{| class="wikitable sortable" cellspacing="1" cellpadding="1" summary="Cisco" border="1"
−
|+ Sektioner i et design dokument - hvad skal med
+
|+ Sections in a Design dokument
 
|- bgcolor="#d3d3d3"
 
|- bgcolor="#d3d3d3"
−
! scope="col" | Sektion
+
! scope="col" | Section
 
! scope="col" | Description  
 
! scope="col" | Description  
 
|-
 
|-
−
| Introduktion || Formål og mål for netværks designet
+
| Introduction || describes the project’s purpose and the reasons for the network design.
 
|-
 
|-
−
| Design krav || Virksomhedens krav og begrænsninger til netværket.
+
| Design Requirements || lists the organization’s requirements, constraints, and goals.
 
|-
 
|-
−
| Nuværende netværk || Netværkstegninger, hard- og softwareversioner og eksisterende konfigurationer.
+
| Existing Network Infrastructure || includes logical (Layer 3) topology diagrams; physical topology diagrams; audit results; routing protocols; a summary of applications; a list of network routers, switches, and other devices; configurations; and a description of issues.
 
|-
 
|-
−
| Design || Ny logisk topologi, design og IP adresseplaner
+
| Design || contains the specific design information, such as logical and physical topology, IP  
 +
addressing, routing protocols, and security configurations.
 
|-
 
|-
−
| Proof of Concept || Resultater fra et pilotprojekt/FAT (Field Acceptence Test)
+
| Proof of Concept || results from live pilot or prototype testing.
 
|-
 
|-
−
| Implementations plan || Detaljeret beskrivelse af installationsfasen.   
+
| Implementation plan || includes the detailed steps for the network staff to implement the new
 +
installation and changes.   
 
|-
 
|-
−
| Bilag || Support information til virksomheden.
+
| Appendixes || contains additional information and configurations.
 
|}
 
|}
−
Optimering af kommunikationen mellem applikationer og services ved at anvende intelligente netværks services som for eksempel sikkerhed, virtualisering og QoS
+
Optimization of communication between applications and services by using intelligent network services such as security, virtualization and Quality of Service (QoS)
 +
 
 
== Links ==
 
== Links ==
 
*[http://www.cisco.com/en/US/netsol/ns629/index.html Cisco SONA]
 
*[http://www.cisco.com/en/US/netsol/ns629/index.html Cisco SONA]

Latest revision as of 12:09, 18 September 2016


Cisco Certified Design Associate

Strategic network design

Cisco Service-Oriented Network Architecure (SONA) describes a model for design of networks. Cisco updated their designmodel from Architecture for Voice, Video and Integrated Data(AVVID) to Intelligent Information Network (IIN).

Cisco SONA three layeer design model

There are three faces in the IIN design.

  1. Integrated transport: Voice, Video and Data are joined and transported together.
  2. Integrated services: For exampel Storage (SAN), voice
  3. Integrated Applications:

Reading plan

See fronter Network Semester 3

Materials

The Book

CCDA Official Exam Certification Guide

  • ISBN: 978-1-58720-177-6

Part I - General Network Design

Part II - LAN and WAN design

Part III - The Internet Protocol and Routing Protocols

Part IV - Security, Convergence and Network Management

Part V - Comprehensive Scenarios

Summary

IIN

IIN faser (Intelligent Information Network)
IIN Phase Description
Integrated Transport Joining voice, data and video in a transport network
Integrated Service Ingegrate common services such as storage, virtualization of network systems
Integrated Application The Network knows the applications, server virtualization

SONA Layer

SONA layer (Service-Oriented Network Architecure)
SONA lag Description
Network Infrastructure layer Contains enterprise servers, storage and clients
Interactive Service Layer Optimizationof communication between applications and services by utilizing intelligent network services such as security, Voice, Virtualization og QoS
Application layer Business applications (Programs) and collaboration tools (mail, voice ...)

SONA Infrastruktur services

SONA Infrastruktur services (Service-Oriented Network Architecure)
SONA lag Description
Identity Services Including AAA, NAC og NBAR
Mobility Services Access to network services regardless of physical location
Storage Services Storage of critical data
Compute Services Enhancing compute resources (Virtualization)
Security Services Security of all resources
Voice and collaboration Services Shared services and programs

PPDIOO

PPDIOO Network live-cycle phases (Prepare, Plan, Design, Implement, Operate og Optimize)
PPDIOO aktivitet Description
Prepare DThe Prepare phase establishes organization and business requirements, develops a network

strategy, and proposes a high-level architecture to support the strategy. Technologies that support the architecture are identified. This phase creates a business case to establish a financial justification for a network strategy.

Plan The Plan phase identifies the network requirements by characterizing and assessing the network,

performing a gap analysis against best-practice architectures, and looking at the operational environment. A project plan is developed to manage the tasks, responsible parties, milestones, and resources to do the design and implementation. This project plan is followed during all phases of the cycle.

Design The network design is developed based on the technical and business requirements obtained from

the previous phases. The network design provides high availability, reliability, security, scalability, and performance. The design includes network diagrams and an equipment list. The project plan is updated with more granular information for implementation. After the Design phase is approved, the Implement phase begins.

Implement New equipment is installed and configured in the Implement phase. New devices replace or

augment the existing infrastructure. The project plan is followed during this phase. Planned network changes should be communicated in change control meetings, with necessary approvals to proceed. Each step in the implementation should includes a description, detailed implementation guidelines, estimated time to implement, rollback steps in case of a failure, and any additional reference information. As changes are implemented they are also tested before moving to the Operate phase.

Operate The Operate phase maintains the network’s day-to-day operational health. Operations include

managing and monitoring network components, routing maintenance, managing upgrades, managing performance, and identifying and correcting network faults. This phase is the design’s final test. During operation, network management stations should monitor the network’s general health and generate traps when certain thresholds are reached.

Optimize The Optimize phase involves proactive network management by identifying and resolving issues

before they affect the network. The Optimize phase may create a modified network design if too many network problems arise, to improve performance issues, or to resolve application issues. The requirement for a modified network design leads to the network life cycle beginning.

Top-down or Bottom-up design

Top-down design

Incorporates the organization’s requirements. Provides the big picture. The design meets current and future requirements.

  • Disadvantages:
    • Time demanding
    • Expensive short term.

Bottom-up design

The design is based on previous experience and allows for a quick solution.

  • Disadvantages:
    • May result in inappropriate design.
    • Organizational requirements are not included.

Sections in a Design dokument

Sections in a Design dokument
Section Description
Introduction describes the project’s purpose and the reasons for the network design.
Design Requirements lists the organization’s requirements, constraints, and goals.
Existing Network Infrastructure includes logical (Layer 3) topology diagrams; physical topology diagrams; audit results; routing protocols; a summary of applications; a list of network routers, switches, and other devices; configurations; and a description of issues.
Design contains the specific design information, such as logical and physical topology, IP

addressing, routing protocols, and security configurations.

Proof of Concept results from live pilot or prototype testing.
Implementation plan includes the detailed steps for the network staff to implement the new

installation and changes.

Appendixes contains additional information and configurations.

Optimization of communication between applications and services by using intelligent network services such as security, virtualization and Quality of Service (QoS)

Links

Retrieved from "http://mars.merhot.dk/w/index.php?title=CCDA_-_en&oldid=35096"