Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 236.1 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureGoalsDesign an IP addressing schemeDesign the internal routing modelDesign the Internet connectivity model6.2 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureIP addressing schemeOne of most important aspects of network designInfluenced by several factorsUse of public or private IP addressesNumber of physical locationsNumber of hosts per physical locationTotal number of hosts in all locationsEstimated broadcast traffic at each physical locationIP summarizationDesigning an IP Addressing Scheme(Skill 1)6.3 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructurePublic IP addressingRequires lease of a block of valid public IP addresses capable of supporting all hosts on internal networkAdvantagesDirect access to Internet for all internal hostsReduced complexityDisadvantagesCostPossible reduction of securityDesigning an IP Addressing Scheme (2)(Skill 1)6.4 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructurePrivate IP addressingCan use any valid private IP address blockAdvantagesDoes not need a block of public IP addressesDirect Internet access is not available to client (increases security and makes firewall configuration easier)DisadvantageMust use Network Address Translation (NAT) device to connect clients to InternetDesigning an IP Addressing Scheme (3)(Skill 1)6.5 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureNumber of physical locations provides a base from which to figure the number of subnets requiredNumber of hosts per physical location and total number of hosts in entire networkNumber of hosts not equivalent to number of usersHosts also include workstations, servers, router ports, managed network devices, SMNP-enabled devices, and network printersTotal number of hosts helps you determine the number of private network addresses requiredNumber of hosts per physical location helps determine how many subnets are needed in that physical locationDesigning an IP Addressing Scheme (4)(Skill 1)6.6 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureFigure 6-1 Calculating a base number of required subnets(Skill 1)6.7 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureFigure 6-2 Summarization example(Skill 1)6.8 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureDesigning internal routing modelMajor component of network designMajor stepsDesigning the topologySpecifying the routing protocol configurationDesigning the Internal Routing Model(Skill 2)6.9 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureDesigning the topologyPrimarily concerned with meeting certain goals of the organizationReliabilityRedundancyPerformanceDesigning the Internal Routing Model (2)(Skill 2)6.10 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureSpecifying the routing protocol configurationEach routing protocol has its own idiosyncrasiesSupported protocolsRouting Information Protocol (RIP) Open Shortest Path First (OSPF) protocolDesigning the Internal Routing Model (3)(Skill 2)6.11 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureRouting Information Protocol (RIP)Simple, easy to enable and configure, but not very secure or efficientImproving efficiency Modifying default timersEnabling Silent RIP on all interfaces that do not contain other RIP routers (keeps RIP from advertising to systems on that subnet)Defining neighbors (disables RIP broadcasting, sends updates by unicast which is more efficient, and improves security)Designing the Internal Routing Model (4)(Skill 2)6.12 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureOpen Shortest Path First (OSPF) protocolMore efficientRouting design is more important and complex than with RIPPrimary component: area designations, used to reduce processor and memory use on routerKeep OSPF areas limited to under 100 routers, or significantly less if area is very active (links unstable, SPF computations common, many paths in network)Designing the Internal Routing Model (5)(Skill 2)6.13 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureFigure 6-4 A large network in a single OSPF area(Skill 2)6.14 © 2004 Pearson Education, Inc.Exam 70-297 Designing a Microsoft® Windows® Server 2003 Active Directory and Network InfrastructureLesson 6: Designing the Network InfrastructureDesigning an Internet connectivity modelPrimary concernsAccess method SecurityAccess methodsDirect connectivity
View Full Document