230 likes | 335 Views
Planning and Troubleshooting Routing and Switching. Overview. Selecting Intermediate Devices Planning an Internet Connectivity Strategy Planning Routing Communications Troubleshooting TCP/IP Routing. Lesson: Selecting Intermediate Devices. Types of Devices When to Use Routing
E N D
Overview • Selecting Intermediate Devices • Planning an Internet Connectivity Strategy • Planning Routing Communications • Troubleshooting TCP/IP Routing
Lesson: Selecting Intermediate Devices • Types of Devices • When to Use Routing • Types of Networking Domains • What Are the Features of Switches? • Virtual LANs • Full-Duplex Transmission in Switched Environments • Guidelines for Selecting an Appropriate Intermediate Device
When to Use Routing Use routing to: • Isolate networks from each other • Provide a start for a secure network implementation Traditional uses of routers • Connecting WANs • Segmenting LANs
Broadcast Domain Segment A Segment B Switch Hub Hub Collision Domain A Collision Domain B Types of Networking Domains
Virtual LANs Layer 3 Switch VLAN 1 VLAN 2 Hub Hub Hub A B C D E F G VLAN CDFG – Broadcast Domain VLAN ABE – Broadcast Domain
Full-Duplex Transmission in Switched Environments Switched Environment Switch Frame A Frame B Frame C Frame D Full-duplex communication
Guidelines for Selecting an Appropriate Intermediate Device • Cost • Ease of implementation • Administration and troubleshooting sophistication • Protocol support • Layer 1 support • Speed • Functionality • Programmability
Planning an Internet Connectivity Strategy • Requirements for an Internet Connectivity Solution • NAT as a Solution for Internet Connectivity • ISA (Proxy) as a Solution for Internet Connectivity • Guidelines for Planning an Internet Connectivity Strategy
Requirements for an Internet Connectivity Solution Internet connectivity requirements • Scalability and fault tolerance • Filtering • User access • Authentication • Bandwidth control • Time-of-day access • Extensibility and flexibility • Application connectivity
NAT as a Solution for Internet Connectivity • Why NAT is a good solution • Same security requirements for all users • Non-routed private network • Required private addressing 131.107.0.9 131.107.0.9 10.10.10.6 10.10.10.10 NAT Table 10.10.10.7 • 10.10.10.0 maps to 131.107.0.9
ISA (Proxy) as a Solution for Internet Connectivity • Why ISA (Proxy) is a good solution • Secure Internet and private network access • Routed or non-routed network • Cache web contents 131.107.0.9 131.107.0.9 Intranet 10.10.10.10 10.10.10.9 10.10.10.8 10.10.10.8 ISA (Proxy) Server • 10.10.10.0 maps to 131.107.0.9 10.10.10.7
Guidelines for Planning an Internet Connectivity Strategy • Define the existing network structure • Define security requirements • Identify connectivity requirements • Select an appropriate solution
Planning Routing Communications • Determining the Appropriate Connection Method • Selecting a Routing Protocol • Guidelines for Planning Router Connectivity
Using IP Packet Filters Corporate Headquarters Branch Office Interface B outbound filter All other protocols SNMP Interface A inbound filter Branch Office ICMP Interface C outbound filter All other protocols All protocols
Guidelines for Planning Router Connectivity • Identify the router connection method • Determine which connectivity options to use • Determine which routing protocol to use • Identify filter settings
Troubleshooting TCP/IP Routing • How to Isolate a Routing Problem • When to Use Each of the Troubleshooting Tools • Troubleshooting TCP/IP Routing
Outside-In Strategy Inside-Out Strategy Can you tracert to remote host? Can you ping the remote host? Is the IP configuration correct? Determine where trace fails No No Correct the configuration No Yes Yes Yes Is the routing table accurate? Correct/delete the incorrect route entries If problem still exists, check route configuration No Can you access the failed system? Yes Yes Can you ping the gateway? Contact network support engineer Check system configuration No No Yes Can you ping interior gateways? Contact the administrator of the failed system Fix configuration problem Use tracert to identify communication breakdown No How to Isolate a Routing Problem Divide-by-Half : Isolate by ½ the connection issue, then isolate by ½ again