book

Juniper Networks Warrior

by Peter Southwick

November 2012

Intermediate to advanced

432 pages

11h 5m

English

O'Reilly Media, Inc.

Read now

Unlock full access

What Is the New Network Platform Architecture?How to Use This BookWhat’s in This Book?A Note About This BookConventions Used in This BookUsing Code ExamplesSafari® Books OnlineHow to Contact UsAcknowledgments
Company ProfileNetworkTraffic FlowNeed for ChangeClass of ServiceDesign Trade-OffsRouting and survivabilityRemote locationsMain locationClass of serviceImplementationPrototype PhaseClass of ServiceCut-OverMain SiteRemote Site JAXRemote Sites PHL and IADBackup Site BNAConclusions
IDP8200 BackgroundCommand-Line InterfaceWeb Management InterfaceNSM ManagementSupport TasksDaily TasksIDP PoliciesRulebase OptimizationOther TasksUpdating the detector engineUpdating IDP appliance OSUpdating attacksConclusion
DiscussionDesign Trade-OffsDecisionConfigurationTake One Configuration: ClusteringTake 2 Configuration: Active/Active without RethsTake 3 Configuration: Active/Active with One-Legged RethsTestingSummary
ProblemQ-in-Q FramingVPLS OverheadSolutionsRFC 4623Customer MTU restrictionsMove the MTUConfigurationsManagementlo0.0AccessProtocolsMPLSBGPOSPFCore Router ConfigurationsDistribution Switch ConfigurationsDistribution Router ConfigurationsRate ControlCPE Switch ConfigurationConclusion
ObjectiveDesignTrade-offsRoutingIBR integrationIDPFilter-based forwardingClusteringConfigurationClusteringSecurityRouting instancesInterfaces, zones, and policiesNATSecurity loggingRoutingBGPOSPFDefault routeOut-of-band management networkImplementationLessons LearnedFeature interactionsNetwork interactionsAdministrative issuesConclusion
Company ProfilePhysical Network TopologyServicesDesign ApproachMX connectivityEX connectivityDeploymentManagement networkDesign Trade-OffsOSPFVPLSBGPMPLSTrade-off choicesConfigurationsBoilerplate ConfigurationMX InterfacesEX Boilerplate and InterfacesOSPFMBGPMPLSRSVPLayer 3 VPNVPLSOBMConclusion
IntroductionClient GoalsDesign Trade-OffsFirewallsRoutingAddressingSurvivabilityRecommended DesignSwitching LayerRouting LayerFirewall LayerVirtualizationConfigurationsEX4200 ConfigurationMX240 ConfigurationFirewall ConfigurationDeploymentInitial ConnectivityThe Maintenance WindowPCI ComplianceSummary

Existing DesignIntroduction to Fibre ChannelProposed DesignConcerns and ResolutionsNamingNetwork qualityNetwork UpgradeAdvantages and Benefits of the SolutionQFX3500 Fibre Channel Gateway ConfigurationsManagement ConfigurationsFibre Channel Gateway Interface ConfigurationDCB ConfigurationEX4500 Transit Switch ConfigurationsInterfaces and VLANsTransit Switch DCB ConfigurationVerificationConclusions
Plans and TopologyPhase 1MX ConfigurationManagement ConfigurationRouting Engine ProtectionPolicy ConfigurationsPrefer to receive an aggregate of the locally assigned addressesNo subnets longer than /24No RFC 1918 prefixesAuthentication on all BGP linksThe ISPs will ignore the use of MEDsThe ISPs will respond to local preferenceThe ISPs will forward a default route if requiredThe ISPs will accept prepending only for the local ASThe ISP will not act as a transit network for any other traffic except for its customersProtocol ConfigurationsOSPFBGPPhase 2Final PhasesConclusion
Original Network ArchitectureWAN ConnectivityAddressingInternal ConnectivityFirewallsProblem DefinitionProposed Solution 1Solution 1 AdvantagesSolution 1 DetailsSolution 1 IssuesProposed Solution 2: OSPF over TunnelsEarly Death of Solution 2Configuration for Solution 2Final Solution: Static Routes over TunnelsSolution AdvantagesSolution IssuesRPF checksDefault gateway failure detectionEmail Server Address ResolutionFirewall ConfigurationsConclusion
RequirementsExisting NetworkRouting ProtocolsSolution OptionsThree-Layer DesignTwo-Layer DesignOne-Tier DesignConfigurationsDeployment ScenarioManagement Staging and TestingTop-of-Rack Switch TestingISP Link TestingProduction ConfigurationCut-OverConclusion