俄勒冈大学网络设计.pptxVIP

Campus Networking WorkshopCore Network DesignRouting ArchitecturesWhere do we route?At the point where we want to limit our layer-2 broadcast domainAt your IP subnet boundaryWe can create more complex topologies using routers and at the same time keep things saneRouting ArchitecturesIf we start with the right topology it will make our network more stableUse a hierarchical approach that makes good use of your traffic patterns and IP address allocationsBe aware that topology and logical design are not the sameRouting ArchitecturesWhat is the right topology?Continue to think of three layersAccessDistributionCoreThinking of layers helps reduce convergence time because of the scope of information to processThese layers should not be confused with your L2 architectureRouting ArchitecturesRouting ArchitecturesAccess LayerMinimum routing informationFeeds traffic into the networkLink sizingProvides network access controlNo spoofingNo broadcast sourcesNo directed broadcastsProvides other edge servicesTagging for QoSTunnel terminationTraffic metering and accountingPolicy-based routingRouting ArchitecturesDistribution LayerGoalsIsolates topology changesControls the routing table sizeAggregates trafficStrategiesRoute summarizationMinimize the number of connections to the coreRouting ArchitecturesCore LayerGoalForwarding packets fastStrategiesClear of network policiesEvery device has full reachability to every destinationFacilitates core redundancyReduces suboptimal routingPrevents routing loopsRouting ArchitecturesDepending in how large your campus is you could use the typical hierarchical model or a subsetTwo collapse core modelsSingle router acts as the network coreAll other routers in the distribution layerSingle router acts as the network coreNo distribution layerAll access layer routers connected to the coreRouting ArchitecturesRouting ArchitecturesWhat to do about your address spaceAssign it as you need it ….. WRONG!Poor summarization has an impact on your network’s stabil