Professional Documents
Culture Documents
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. This is an HP copyrighted work that may not be reproduced without the written permission of HP. You may not use these materials to deliver training to any person outside of your organization without the written permission of HP. HP Switching and Routing Technologies Web-based Training Course Companion Rev. 10.41
Introduction
Module 1 Objectives
This module will introduce you to some of the challenges involved in providing high-quality voice and video on an existing data network. After completing this module, you will be able to: Identify business and technological forces that have driven the development of converged networks Describe how HP networking products can meet converged network demand for high availability and predictability
IP Telephony
Video surveillance
While these integrated applications enhance user productivity, they place additional requirements on the infrastructure i f Some applications may require the added flexibility provided by wireless access. Video application support can mean high bandwidth at the edge, with even higher bandwidth requirements at the distribution and core layers. Network devices must support controls that enable prioritized handling for time-sensitive traffic.
Rev. 10.41
1-1
Introduction
Links that are active for Instance 1 Links that are active for Instance 2
Hosts in VLANs mapped to Instance 1 Hosts in VLANs mapped to Instance 2 Hosts in VLANs mapped to Instance 1 Hosts in VLANs mapped to Instance 2
Rev. 10.41
1-2
Introduction
Rev. 10.41
1-3
Introduction
Phone 1
Phone 2
LLDP-MED
The phone identifies itself as a VOIP ,p providing g manufacturer and device, other inventory information The phone adds appropriate 802.1Q tag and priority settings to the traffic it generates.
The switch dynamically places the IP phone in appropriate p pp p VLAN and reports the VLAN ID to the phone. Switch applies policies that will ensure voice quality.
You will learn more about LLDP-MED and other topics relating to Quality of Service in Module 6.
Rev. 10.41
1-4
Introduction
Module 1 Summary
In this module, you learned about traffic control and high availability features required to successfully support a converged network.
Rev. 10.41
1-5
Lesson 1 Introduction: 1
The source and destination IP addresses do not change as packets make their way to the Server. Source and destination MAC addresses change with every router hop.
Payload
10 119215 10.1.192.15
While the Layer 3 header on the packets from Host1 to the Server contains the actual source and destination IP addresses, the Layer 2 header indicates that traffic is destined for the Host1s default gateway, Router1.
Router1
10.1.10.1/24
Router1 Host1 Dest. Source MAC header Host1 Server Source Dest. IP header Payload
Switch
All IP hosts require a gateway in their local address range to reach non-local destinations.
Rev. 10.41
2-1
Lesson 1 Introduction: 2
If this router, or the path between the host and the router, becomes unavailable, the hosts open sessions terminate. Even if an alternate path to remote destinations is available, the host may be unable to detect it. Regardless of the IP address assigned to the second router interface, its physical MAC address is different from that of the failed router interface. i t f The host will need to reconfigure its default gateway and establish new sessions. The replacement router interface cannot assume forwarding responsibility for open sessions. The Virtual Router Redundancy Protocol (VRRP) may be used to establish an active/standby model for default gateways, enabling the standby to resume forwarding responsibilities for existing sessions and those established subsequent to failure of the active gateway.
Switch Router1
All destinations outside 10.1.10.0/24
10 119215 10.1.192.15
Router2
VRRP Terminology
Version 2 of the Virtual Router Redundancy Protocol (VRRP) , which is specified in RFC 3768, provides an industry standard for automatic default gateway failover. A VRRP virtual router is a set of router interfaces on the same network with a common: Virtual Router Identifier (VRID) Virtual IP Address The Owner is the router interface whose actual IP address matches the virtual IP address. Owner (Master)
Actual IP address: VLAN 10: 10.1.10.1/24
Router1
Non-owner (Backup)
Actual IP address: VLAN 10: 10.1.10.2/24
Router1
10.1.10.1
10.1.10.1
Switch1
Rev. 10.41
2-2
00:00:5e:00:01:01 First 40 bits specified in RFC 3768 Last 8 bits = Virtual Router ID Non-owner (Backup)
Actual IP address: VLAN 10: 10.1.10.2/24
Router1
Owner (Master)
Actual IP address: VLAN 10: 10.1.10.1/24
Router1
10.1.10.1
VLAN 10 - Virtual Router ID: 1 Virtual IP address: 10.1.10.1 Virtual MAC: 00:00:5e:00:01:01
10.1.10.1
Switch1
Ethernet header: Destination: Broadcast ff:ff:ff:ff:ff:ff) Source: IETF-VRRP-Virtual-Router-VRID-01 IETF VRRP Virtual Router VRID 01 (00:00:5e:00:01:01) Type: ARP (0x0806) Address Resolution Protocol header: Virtual Router ID Hardware type: Ethernet Protocol type: IP Sender MAC Address: IETF-VRRP-Virtual-Router-VRID-01 (00:00:5e:00:01:01) Sender IP Address: 10.1.10.1 Target MAC Address: Broadcast (ff:ff:ff:ff:ff:ff) The defining characteristic of a Gratuitous ARP message is the Target IP Address: 10.1.10.1 combination of broadcast as the Target MAC address, and
Virtual IP Address
matching values for Source and Target IP address. address The message causes each host in this network to add the following association to its ARP cache: IP Address 10.1.10.1 = MAC Address 00:00:5e:00:01:01
Rev. 10.41
2-3
VRRP Advertisements
The VRRP Master indicates its availability by sending periodic advertisements to the VRRP multicast address, which is 224.0.0.18. The VRRP Master broadcasts a gratuitous ARP request that causes hosts on the VLAN to create an ARP cache entry associating the virtual IP address with the virtual MAC address.
Ethernet header: Destination: 01:00:5e:00:00:12 Source: 00:00:5e:00:01:01 Type: IP (0x0800) IP datagram header: Protocol: VRRP (0x70) Source: 10.1.10.1 Destination: 224.0.0.18 Virtual Router Redundancy Protocol header: Version: 2 Packet type: Advertisement (1) Virtual Router ID: 1 P i it 255 Priority: Count IP Addrs: 1 Auth Type: No authentication (0) Advertisement Interval: 1 (sec) IP Address: 10.1.10.1
This advertisement is sent to the multicast address assigned to VRRP in RFC 3768
This priority level indicates that the originator of this message is the owner of the Virtual IP Address. A copy if this advertisement is sent once per second.
Rev. 10.41
2-4
Load Sharing
VRRP routers often support multiple VRIDs. In this implementation shown in the diagram, either router can be Owner of any of the VRIDs. While the VRRP Backup for a given VLAN does not act as gateway for its hosts, the router interface is fully functional. Traffic that enters a router through a VRRP Master interface can be forwarded onto a different VLAN through a Backup interface.
VLAN 10 - VRID: 1: 10.1.10.1 Virtual MAC: 00:00:5e:00:01:01 VLAN 20 : VRID 2: 10.1.20.1 Virtual MAC: 00:00:5e:00:01:02
Switch1
Switch1
Rev. 10.41
2-5
Switch1
Lesson 2 Introduction
To enhance default gateway availability for client PCs, network designers often specify the use of redundant uplinks from edge switches to routers. Hosts in two VLANs are distributed over two edge switches. The edge switches have redundant uplinks to a pair of routing switches that will support VRRP. All switch-to-switch links are members of both user VLANs. This lesson will describe some challenges and solutions that arise when VRRP and the Spanning Tree Protocol (STP) are combined within the same domain.
VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 Bridge Priority 0 (Root) Router1
Tagged 10 20 10 10 20 20
VLAN 10: 10.1.10.2/24 VLAN 20: 10.1.20.2/24 Bridge Priority 4096 (Backup Root) Router2
Tagged
10 20 Tagged
Tagged
10 20
Tagged
Switch1 VLAN 10 Hosts: 10.1.10.0/24 VLAN 20 Hosts: 10.1.20.0/24 VLAN 10 Hosts: 10.1.10.0/24
Switch2
Rev. 10.41
2-6
B Switch1
B Switch2
Router1
Payload
VLAN 10: 10.1.10.2/24 VLAN 20: 10.1.20.2/24 Bridge Priority 4096 (Backup Root)
Router2
Payload
Because Router1 is Host As gateway, its MAC address appears in the packets Layer 2 header.
Rev. 10.41
2-7
VLAN 10: 10.1.10.2/24 VLAN 20: 10.1.20.2/24 Bridge Priority 4096 (Backup Root)
Router1
Router2
Payload
Payload
Router2 is the default gateway for Host B. However, the uplink from Switch 2 to Router 2 is in Blocking state.
VLAN 10: 10.1.10.2/24 VLAN 20: 10.1.20.2/24 Bridge Priority 4096 (Backup Root)
Router1
Router2
Payload
Rev. 10.41
2-8
Router1
Router2
Module 2 Summary
In this module, you learned the elements involved in the configuration of VRRP and MSTP. Topics included: The roles of Master and Backup routers in transmitting and receiving VRRP v2 advertisements Interactions I t ti among VRRP advertisements d ti t and d links li k blocked bl k d b by S Spanning i T Tree How the configuration of Multiple Spanning Tree instances enables routers to share gateway responsibilities
Rev. 10.41
2-9
IP Routing
Module 3: IP Routing
Objectives
A routing switch forwards traffic between its interfaces to enable communication among any combination of local and remote networks. After completing this module, you will be able to: Categorize the possible sources of routing information. information Describe how an IP router makes a forwarding decision when a packets destination matches with multiple route table entries. List the differences between automatic and manual summarization of remote IP address space. Describe how a router determines which route to place in its route table when the same address range is advertised by different routing protocols or methods.
Lesson 1 Introduction
While Layer 2 switches enable connectivity among devices within a network, the function of a router or Layer 3 switch is to interconnect networks. It uses a packets Layer 3 information to determine which of its interfaces leads to the destination, and creates a new Layer 2 header for each packet it forwards forwards. Routers may pass traffic between a pair of hosts located on directly connected networks. The packets Layer 2 header contains the MAC address of the interface that provides default gateway service for Network 1. The router removes the existing Layer 2 header and creates a new header with HostBs MAC address as the destination. A router may participate in forwarding traffic destined for remote hosts. The new Layer 2 header contains the MAC address of the next router on the path to the destination host.
RouterA
S it h2 Switch2
HostB: Network 2
HostA: Network 1
HostC: Network 4
Rev. 10.41
3-1
IP Routing
A router forwards traffic destined for local networks using the interface indicated in the IP route table. The router drops traffic destined for address ranges not in the table.
Router interface 1: IP address: 10.1.10.1/24 Subnet mask: 255.255.255.0 Hosts in the range: 10.1.20.0/24
R RouterA A
Router interface 2: IP address: 10.1.20.1/24 Subnet mask: 255.255.255.0 Hosts in the range: 10.1.20.0/24
Loopback 0: 10.1.0.25
RouterA
Switch1
Rev. 10.41
3-2
IP Routing
VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 100: 10 10.1.100.1/24 1 100 1/24 Loop 0: 10.1.0.25/32
RouterA
10.1.30.0/24 10.1.40.0/24 10.1.0.26/32 VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 Loop 0: 10.1.0.26/32
RouterB
RouterA
This command, Th d issued d at the h CLI of f RouterB, R B provides d information the router will use to forward traffic toward the destination network 10.1.10.0/24
ip route 10.1.10.0/24 10.1.100.1 1 Network topology, including Internet and intranet connectivity, determine appropriate methods for each situation.
VLAN 100: 10.1.100.2/24 VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 Loop 0: 10.1.0.26/32
RouterB
Rev. 10.41
3-3
IP Routing
BGP
Exterior Gateway Protocols (EGP) facilitate the exchange of route information among routers in different Autonomous Systems. Border Gateway Protocol version 4 (BGP4) is i the h current standard d d EGP for Internet connectivity Internet Service Providers often use an IGP, such as IS-IS, within their own networks to enable connectivity among BGP routers.
BGP
Route table Destination D ti ti C t Next Cost N th hop Network 1 3 Router2 Network 2 3 Router2 Network 3 2 Router2 Network 4 1 connected
Rev. 10.41
3-4
IP Routing
R1 advertisement
Network 4
Lesson 2 Introduction
The Routing Information Protocol (RIP) is easy to configure, and is suitable for small- to medium-sized networks. Each router reports its known routes and their cost, to its neighbors The information is passed from one router to neighbors. another, with costs incrementing at every hop. RIPs main disadvantage is slow convergence. Changes in routing topology may propagate slowly because the information is acquired from routers that may be as many as 15 hops away. In this lesson, you will learn RIPs rules and how to p RIP routes as they y appear pp in the route table. interpret
Rev. 10.41
3-5
IP Routing
RIP Advertisements: 1
The Routing Information Protocol (RIP) uses a distancevector algorithm to determine the best path to each destination. Routers periodically advertise their route table entries g , or p peers. to RIP neighbors, The advertisements contain a list of known address ranges (vectors), each of which is paired with the cost (distance) of the entire path to the address range.
VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 100: 10.1.100.1/24 Loop 0: 10.1.0.25/32
RouterA
10.1.100.1/24
10.1.100.2/24 VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 Loop 0: 10.1.0.26/32
RouterB
RIP Advertisements: 2
VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 100: 10.1.100.1/24 Loop 0: 10.1.0.25/32
Ethernet header: Dest: 01005e-000009 Source: <RouterA MAC> IP datagram d t h header: d Protocol: UDP Source: 10.1.100.1 Dest: 224.0.0.9 UDP header: Source: 520 (RIP) Dest: 520 (RIP)
RIP v2 updates are sent to a reserved multicast address
RouterA
10.1.100.1/24
R I P
Routing Information Protocol: Command: Response (2) Version: RIPv2 (2) Network: 10.1.0.25 Mask: 255.255.255.255 Metric: 1 Network: 10.1.10.0 Mask: 255.255.255.0 Metric: 1 Network: 10.1.20.0 Mask: 255.255.255.0 Metric: 1 Ethernet trailer: <Checksum value>
This router is configured to use split horizon loop prevention. It does not include 10.1.100.0/24, which is the address range associated with the network that carries this RIP update.
U D P I P M A C
10.1.100.2/24 VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 Loop 0: 10.1.0.26/32
RouterB
Rev. 10.41
3-6
IP Routing
RouterA
10.1.100.1/24
10.1.100.2/24 VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 Loop 0: 10.1.0.26/32
RouterB
10.1.100.1/24
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 Loop 0: 10.1.0.27/32
10.1.100.2/24
RouterC
.1
10.1.101.0/24
.2
RouterB
Rev. 10.41
3-7
IP Routing
RouterA
10.1.100.1/24
10.1.100.2/24
RouterC
.1
10.1.101.0/24
.2
RouterB
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 Loop 0: 10.1.0.27/32
10.1.100.2/24
RouterC
.1
10.1.101.0/24
.2
RouterB
Rev. 10.41
3-8
IP Routing
RouterA
.2
.1
Connected networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 100: 10.1.100.1/24 VLAN 102 102: 10 10.1.102.2/24 1 102 2/24 Loop 0: 10.1.0.25/32
10.1.102.0/24 10.1.100.0/24
.1
.2
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 VLAN 102: 10.1.102.1/24 Loop 0: 10.1.0.27/32
RouterC
.1
RouterB
10.1.101.0/24
.2
Connected networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 VLAN 101: 10.1.101.2/24 Loop 0: 10.1.0.26/32
RouterA
.2
.1
Connected networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 100: 10.1.100.1/24 VLAN 102 102: 10 10.1.102.2/24 1 102 2/24 Loop 0: 10.1.0.25/32
10.1.102.0/24 10.1.100.0/24
.1
.2
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 VLAN 102: 10.1.102.1/24 Loop 0: 10.1.0.27/32
RouterC
.1
RouterB
10.1.101.0/24
.2
Connected networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 VLAN 101: 10.1.101.2/24 Loop 0: 10.1.0.26/32
Rev. 10.41
3-9
IP Routing
Connected networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 100: 10.1.100.1/24 Source: 10.1.102.2 Dest: 224.0.0.9 VLAN 102 102: 10 10.1.102.2/24 1 102 2/24 UDP header: .2 (RIP) .1 Loop Source: 520 Dest: 520 (RIP) 0: 10.1.0.25/32
Routing Information Protocol: Network: 10.1.0.25 Mask: 255.255.255.255 Metric: 1 Network: 10.1.0.26 Mask: 255.255.255.255 Metric: 2 Network: 10.1.0.27 Mask: 255.255.255.255 Metric: 3 Network: 10.1.10.0 Mask: 255.255.255.0 Metric: 1 Network: 10.1.20.0 Mask: 255.255.255.0 Metric: 1 Network: 10.1.30.0 Mask: 255.255.255.0 Metric: 2 Network: 10.1.40.0 Mask: 255.255.255.0 Metric: 2 10.1.100.0/24 Network: 10.1.50.0 Mask: 255.255.255.0 Metric: 3 Network: 10.1.60.0 Mask: 255.255.255.0 Metric: 3 Network: 10.1.100.0 Mask: 255.255.255.0 Metric: 1 Network: 10.1.101.0 Mask: 255.255.255.0 Metric: 2
.1
.2
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 VLAN 102: 10.1.102.1/24 Loop 0: 10.1.0.27/32
RouterC
.1
RouterB
10.1.101.0/24
.2
Connected networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 VLAN 101: 10.1.101.2/24 Loop 0: 10.1.0.26/32
.2
.1
10.1.102.0/24 10.1.100.0/24
.2
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 VLAN 102: 10.1.102.1/24 Loop 0: 10.1.0.27/32
RouterC
.1
.1 10.1.101.0/24 .2
RouterB
Connected networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 VLAN 101: 10.1.101.2/24 Loop 0: 10.1.0.26/32
Rev. 10.41
3 - 10
IP Routing
RouterA
.2
.1
Connected networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 100: 10.1.100.1/24 VLAN 102 102: 10 10.1.102.2/24 1 102 2/24 Loop 0: 10.1.0.25/32
10.1.102.0/24 10.1.100.0/24
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 VLAN 102: 10.1.102.1/24 Loop 0: 10.1.0.27/32
RouterC
.1
.1
Network: 10.1.0.26 Mask: 255.255.255.255 Metric: 2 Network: 10.1.0.27 Mask: 255.255.255.255 Metric: 1 .2 Network: 10.1.30.0 Mask: 255.255.255.0 Metric: 2 Network: 10.1.40.0 Mask: 255.255.255.0 Metric: 2 Connected networks: RouterB Network: 10.1.50.0 Mask: 255.255.255.0 1 VLAN Metric: 30: 10.1.30.1/24 10.1.101.0/24 Network: 10.1.60.0 Mask: 255.255.255.0 Metric: 1 VLAN 40: 10.1.40.1/24 .2 Network: 10.1.100.0 Mask: 255.255.255.0 Metric: 2 VLAN 100: 10.1.100.2/24 Network: 10.1.101.0 Mask: 255.255.255.0 Metric: 1 VLAN 101: 10.1.101.2/24 Loop 0: 10.1.0.26/32
.2
.1
.2
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 VLAN 102: 10.1.102.1/24 Loop 0: 10.1.0.27/32
RouterC
.1
.1 10.1.101.0/24 .2
RouterB
Connected networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 VLAN 101: 10.1.101.2/24 Loop 0: 10.1.0.26/32
Rev. 10.41
3 - 11
IP Routing
RouterA
.2
.1
Connected networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 100: 10.1.100.1/24 VLAN 102 102: 10 10.1.102.2/24 1 102 2/24 Loop 0: 10.1.0.25/32
RIP advertisement : RouterC int 10.1.102.1 Network: 10.1.0.26 Mask: 255.255.255.255 Metric: 16 10.1.102.0/24 Network: 10.1.0.26 Mask: 255.255.255.255 Metric: 2 Network: 10.1.0.27 Mask: 255.255.255.255 Metric: 1 Network: 10.1.10.0 Mask:10.1.100.0/24 255.255.255.0 Metric: 16 Network: 10.1.20.0 Mask: 255.255.255.0 Metric: 16 Network: 10.1.30.0 Mask: 255.255.255.0 Metric: 2 N t Network: k 10 10.1.40.0 1 40 0 M Mask: k 255 255.255.255.0 255 255 0 M Metric: ti 2 Network: 10.1.50.0 Mask: 255.255.255.0 Metric: 1 Network: 10.1.60.0 Mask: 255.255.255.0 Metric: 1 Network: 10.1.100.0 Mask: 255.255.255.0 Metric: 2 Network: 10.1.101.0 Mask: 255.255.255.0 Metric: 1 .2
Connected networks: VLAN 50: 10.1.50.1/24 VLAN 60: 10.1.60.1/24 VLAN 101: 10.1.101.1/24 VLAN 102: 10.1.102.1/24 Loop 0: 10.1.0.27/32
RouterC
.1
.1 10.1.101.0/24 .2
RouterB
Connected networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 100: 10.1.100.2/24 VLAN 101: 10.1.101.2/24 Loop 0: 10.1.0.26/32
172.16.101.0/24
Loop 0: 172.16.0.25/32 VLAN 10: 172.16.10.1/24 VLAN 20: 172.16.20.1/24 VLAN 100: 10.0.100.1/24 VLAN 101: 172.16.101.2/24
RouterD
RouterA
RIP advertisement : RouterC int 10.1.102.1 Network: 10.0.100.0 Mask: 255.255.255.0 Metric: 16 Network: 10.1.0.25 Mask: 255.255.255.255 Metric: 16 Network: 10.1.0.26 Mask: 255.255.255.255 Metric: 16 Network: 10.1.0.27 Mask: 255.255.255.255 Metric: 16 Network: 10.1.10.0 Mask: 255.255.255.0 Metric: 16 Network: 10.1.20.0 Mask: 255.255.255.0 Metric: 16 Network: 10.1.101.0 Mask: 255.255.255.0 Metric: 16 Network: 172.16.0.0 Mask: 255.255.0.0 Metric: 1
.1 10.0.100.0/24
RouterC
RouterB
Rev. 10.41
3 - 12
IP Routing
Loop 0: 172.16.0.25/32 VLAN 10: 172.16.10.1/24 VLAN 20: 172.16.20.1/24 VLAN 100: 10.0.100.1/24 VLAN 101: 172.16.101.2/24
When it sends RIP updates over VLAN 101, 101 Router D uses a single advertisement to summarize the address space within 10.0.0.0/8. It advertises individual networks within the 172.16.0.0/16 range because the address associated with the VLAN 101 is within that range.
Lesson 3 Introduction
Dynamic routing protocols may need to be selectively enabled to control the flow of routing updates. Static routes may be selectively used in place of dynamic updates to minimize unnecessary overhead. In this lesson, you will learn how to summarize contiguous address space using static routes.
Rev. 10.41
3 - 13
IP Routing
Rev. 10.41
3 - 14
IP Routing
Summarization by Location
The intranet core routers in this example can also use a static routes to summarize remote address space. Routers in the intranet core will be configured with a static route for each address range. The next hop for each range will be a neighboring router interface at the remote location. Network summarization requires that all networks within the summarized range must be reachable through the next hop router interface.
RC
RA
RB
Rev. 10.41
3 - 15
IP Routing
RC2 RC1
RB2
Rev. 10.41
3 - 16
IP Routing
Administrative Distance
Each routing protocol applies its own interpretation to the metric value. Administrative distance provides a way for administrators to assign preference to one source of routing information over another. Administrative distances may be modified from the system defaults.
IP Route Table
Destination 0.0.0.0 10.0.100.0/24 10.1.0.0/16 10.1.1.0/24 10.1.2.0/24 10.1.10.0/24 10.1.20.0/24 10.1.30.0/24 10.1.40.0/24 10.1.64.0/24 10.2.0.0/16 Gateway 10.0.100.100 VLAN100 10.0.102.1 VLAN1 VLAN2 10.1.64.2 10.1.64.2 VLAN30 VLAN40 VLAN64 10.0.100.2 VLAN 100 100 102 1 2 64 64 30 40 64 100 Type static connected static connected connected rip rip connected connected connected static Metric 1 1 1 1 1 3 3 1 1 1 1 Distance 1 0 1 0 0 120 120 0 0 0 1
Default administrative distances for this router: Directly connected networks: 0 Static routes: 1 RIP-learned routes: 120 OSPF-learned OSPF learned routes: 1 10
Static route was defined here: ip route 0.0.0.0/0 10.0.100.100 Router A2: IP Route Table
Destination 0.0.0.0 10.1.1.0/24 10.1.10.0/24 10.1.20.0/24 10.1.30.0/24 10.1.40.0/24 ... 10.1.64.0/24 Gateway 10.1.64.1 VLAN1 VLAN10 VLAN20 10.1.64.1 10.1.64.1 VLAN64 VLAN 64 1 64 64 64 64 64 Type rip connected rip rip rip connected connected Metric 2 1 3 3 2 1 1 Distance 120 0 120 120 120 0 0
A1
A3
A2 A4
Rev. 10.41
3 - 17
IP Routing
Module 3 Summary
This module described basic IP routing concepts as they apply to forwarding among local and remote networks. Topics included: IP route table interpretation The categories of IP routing protocols RIP advertisements Using static routes to summarize address space
Rev. 10.41
3 - 18
Lesson 1 Introduction
OSPF has several advantages over RIP. 1. OSPF scales to larger intranets. OSPF interfaces may be assigned metrics that are sensitive to the supported bandwidth. E h router Each t i is able bl t to consider id li link k speed d when h selecting the shortest path to a given destination. OSPF does not place a specific limit on network diameter. 2. OSPF router advertisements are more reliable. An OSPF router advertisement describes the type, cost, and network address associated with its connected networks. An OSPF router floods advertisements from its neighbors to all other neighbors intact, without changing the contents of the advertisements.
Network B Cost 10 Network C Cost 100
R1
Rev. 10.41
4-1
10.1.0.32
10.2.0.32
10.1.0.33
10.2.0.33
Rev. 10.41
4-2
Rev. 10.41
4-3
Area 1.0.0.0
OSPF Router 10.1.0.32 Area 0.0.0.0 Networks: VLAN 100: 10.0.100.2/24 / Area 1.0.0.0 Networks: Loop 0: 10.1.0.32/32 VLAN 64: 10.1.64.1/24 VLAN 65: 10.1.65.1/24 VLAN 67: 10.1.67.1/24
OSPF Router 10.1.0.33 Area 0.0.0.0 Networks: VLAN 100: 10.0.100.3/24 / Area 1.0.0.0 Networks: Loop 0: 10.1.0.33/32 VLAN 64: 10.1.64.2/24 VLAN 66: 10.1.66.1/24 VLAN 68: 10.1.68.1/24
OSPF Router 10.1.0.34 Area 1.0.0.0 Networks: p 0: 10.1.0.34/32 / Loop VLAN 65: 10.1.65.2/24 VLAN 68: 10.1.68.2/24 VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24
10.1.10.0/24 10.1.20.0/24
All interfaces of each non-ABR are located within the same area.
10.1.30.0/24 10.1.40.0/24
OSPF Router 10.1.0.35 Area 1.0.0.0 Networks: oop 0: 10.1.0.35/32 0. .0.35/3 Loop VLAN 66: 10.1.66.2/24 VLAN 67: 10.1.67.2/24 VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24
Rev. 10.41
4-4
Data: 255.255.255.255 Metric: 1 Data: 255.255.255.0 Metric: 1 Data: 255.255.255.0 Metric: 1 Data: 255.255.255.0 Metric: 1
ID: 10.1.0.26
RouterB
The networks are considered Stub type because the router has no adjacent neighbors on these networks.
O S P F I P M A C
OSPF Header: OSPF Version: 2 Message Type: Hello packet (1) Source OSPF Router: 10.1.0.25 Area: 1.0.0.0 OSPF Hello Packet Header: Network Mask: 255.255.255.0 This router has no Hello interval: 10 seconds neighbors on this Router Priority: 1 network. It assumes the Router Dead Interval: 40 seconds role of Designated Router. Designated Router: 10.1.64.1 Backup Designated Router: 0.0.0.0
ID: 10.1.0.26
RouterB
Rev. 10.41
4-5
O S P F I P M A C
ID: 10.1.0.26
RouterB
O S P F I P M A C
ID: 10.1.0.26
RouterB
Rev. 10.41
4-6
OSPF Area 1.0.0.0 Networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 64: 10.1.64.2/24 Loop 0: 10.1.0.26/32
ID: 10.1.0.26
RouterB
These items identify this message as the first instance of the Router LSA advertised by Router ID 10.1.0.25.
OSPF Area 1.0.0.0 Networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 64: 10.1.64.2/24 Loop 0: 10.1.0.26/32
ID: 10.1.0.26
RouterB
Rev. 10.41
4-7
OSPF Area 1.0.0.0 Networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 64: 10.1.64.1/24 Loop 0: 10.1.0.25/32
RouterA
ID: 10.1.0.25
RouterB
Ethernet header: Dest: <RouterA MAC> Source: <RouterB MAC> IP datagram header: Protocol: 89 (OSPF) Source: 10.1.64.2 Dest: 10.1.64.1 OSPF Header: OSPF Version: 2 Message Type: LS Request (3) Source OSPF Router: 10.1.0.26 Area: 1.0.0.0 Link State Request Header: LSA Type: Router LSA (1) Link State ID: 10.1.0.25 10 1 0 25 Advertising Router: 10.1.0.25 LS Sequence Number: 80000000
RouterB includes header information for the LSAs required to synchronize its database with RouterA.
Rev. 10.41
4-8
While the Database Description and Link State Request packets include only LSA headers, the Link State Update packet provides detail about the advertising routers connected networks.
OSPF Area 1.0.0.0 Networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 64: 10.1.64.1/24 Loop 0: 10.1.0.25/32
RouterA
ID: 10.1.0.25
RouterB
Rev. 10.41
4-9
Like the Link State Request, the acknowledgment contains LSA header information. If RouterA does not receive an acknowledgment, it will retransmit the Link State Update.
RouterA
ID: 10.1.0.25
Hello
Hello OSPF Area 1.0.0.0 Networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 64: 10.1.64.2/24 Loop 0: 10.1.0.26/32
ID: 10.1.0.26
RouterB
Rev. 10.41
4 - 10
RouterA
ID: 10.1.0.25
OSPF Area 1.0.0.0 Networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 64: 10.1.64.2/24 Loop 0: 10.1.0.26/32
ID: 10.1.0.26
RouterB
Number of Links: 4 As soon routers have completed forming their Type: Stub as (3) these Link ID: 10.1.0.25 Link Data: 255.255.255.255 Type: Stub (3) the elected Link ID: 10.1.10.0 Link Data: 255.255.255.0 adjacency, Designated Router (DR) generates Type: Stub (3) Link ID: 10.1.20.0 Link Data: 255.255.255.0 a second LSA type, known as a Network LSA. Type: Transit (2) Link ID: 10.1.64.1 Link Data: 10.1.64.1 Router LSA (1)have synchronized link LinkAdjacent State Advertisement Type: neighbors must always Link State ID: 10.1.0.26 state databases. This requirement causes the DR to Advertising Router: 10.1.0.26 immediately Number of Links: 4 send the new Network LSA to its neighbors. Type: Stub (3) Link ID: 10.1.0.26 Link Data: 255.255.255.255 T Type: St Stub b (3) Li k ID Link ID: 10 10.1.30.0 1 30 0 Link Li k D Data: t 255 255.255.255.0 255 255 0 Type: Stub (3) Link ID: 10.1.40.0 Link Data: 255.255.255.0 Type: Transit (2) Link ID: 10.1.64.2 Link Data: 10.1.64.1 Link State Advertisement Type: Network LSA (2) Link State ID: 10.1.64.1 Advertising Router: 10.1.0.25 Netmask: 255.255.255.0 Attached Router: 10.1.0.25 Attached Router: 10.1.0.26
You can issue CLI commands that will display the routers role Link State Advertisement Type: Router LSA (1) a ID: multi-access Linkon 10.1.0.25 State 10 1 0 25 network. This information is also included in Hello messages sent by any neighbor on the network. Advertising Router: 10.1.0.25
Metric: 1 Metric: 1 Metric: 1 Metric: 1
RouterA
ID: 10.1.0.25
Metric: 1 M ti 1 Metric: Metric: 1 Metric: 1 OSPF Area 1.0.0.0 Networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 64: 10.1.64.2/24 Loop 0: 10.1.0.26/32
ID: 10.1.0.26
RouterB
Rev. 10.41
4 - 11
RouterB
ID: 10.1.0.26 10 1 0 26
13
OSPF Area 1.0.0.0 Networks: VLAN 50: 10.1.30.1/24 VLAN 60: 10.1.40.1/24 VLAN 65: 10.1.65.1/24 Loop 0: 10.1.0.26/32
3
OSPF Area 1.0.0.0 Networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 64: 10.1.64.2/24 VLAN 65: 10.1.65.2/24 Loop 0: 10.1.0.26/32
OSPF Area 1.0.0.0 Networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 64: 10.1.64.1/24 Loop 0: 10.1.0.25/32 RouterA
ID: 10.1.0.25
16
OSPF Area 1.0.0.0 Networks: VLAN 50: 10.1.30.1/24 VLAN 60: 10.1.40.1/24 VLAN 65: 10.1.65.1/24 Loop 0: 10.1.0.26/32
16
OSPF Area 1.0.0.0 Networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 64: 10.1.64.2/24 VLAN 65: 10.1.65.2/24 Loop 0: 10.1.0.26/32
Rev. 10.41
4 - 12
OSPF Area 1.0.0.0 Networks: VLAN 10: 10.1.10.1/24 VLAN 20: 10.1.20.1/24 VLAN 64: 10.1.64.1/24 Loop 0: 10.1.0.25/32 RouterA
ID: 10.1.0.25
16
Hello DB Description Link State Request Link State Update Li k St Link State t Ack A k
Link-state Update Packet RouterB
ID: 10.1.0.26 10 1 0 26
16
OSPF Area 1.0.0.0 Networks: VLAN 50: 10.1.30.1/24 VLAN 60: 10.1.40.1/24 VLAN 65: 10.1.65.1/24 Loop 0: 10.1.0.26/32
16
OSPF Area 1.0.0.0 Networks: VLAN 30: 10.1.30.1/24 VLAN 40: 10.1.40.1/24 VLAN 64: 10.1.64.2/24 VLAN 65: 10.1.65.2/24 Loop 0: 10.1.0.26/32
Rev. 10.41
4 - 13
BDR
NonDR 2
NonDR 3
BDR
NonDR 2
NonDR 3
Rev. 10.41
4 - 14
Rev. 10.41
4 - 15
Link-State Database
Graph
Shortest-path tree
The graph uses a one-way arrow to represent stub networks. It represents point-to-point networks using two arrows. This router represents its point-to-point link using an arrow that points to th router the t on th the other th side id of f th the link. Router 10.1.0.33 represents its own side of the point-to-point link using an arrow that connects to Router 10.1.0.32. Router 10.1.0.33s loopback interface is shown as a stub network. This router also has a connection to a multi-access transit network.
Network: 10.1.64.3
OSPF does not require that point-to-point links be assigned an IP address. An unnumbered point-to-point network would be graphed as it is currently shown. However, this example does assign address space to the link, link so our graph represents this address space as two stub links links.
Rev. 10.41
4 - 16
The Designated Router of the multi-access network originates the Network LSA. The graph includes an arrow from the Network vertex to the DRs vertex. The graph uses arrows to represent other routers attached to this network.
Network: 10.1.64.3
Router: 10.1.0.35
The Designated Router of the multi-access network originates the Network LSA. The graph includes an arrow from the Network vertex to the DRs vertex. The graph uses arrows to represent other routers attached to this network. The networks connected to routers 10.1.0.34 and 10.1.0.35 are graphed using the same procedure.
Network: 10.1.64.3
Router: 10.1.0.35
Rev. 10.41
4 - 17
Router and Network entries are directly based on Router and Network link-state advertisements. Sequence numbers reflect the most current instances of each LSA. Stub link entries are derived from information in Router LSAs. No sequence numbers are assigned. While transit networks carry traffic destined for other networks, stub links are analogous to leaves on the shortest-path tree.
Network10.1.129.0/24
Network10.1.130.0/24
Rev. 10.41
4 - 18
Lesson 2 Introduction
Fast convergence is one of OSPFs main benefits. However, the mechanisms that enable OSPF routers to quickly respond to state changes and maintain current information can negatively affect performance if the scope of router and network link state advertisements is too large. Like intranets that use RIP, those that use OSPF will benefit from the summarization of remote address space. However, OSPF intranets are not limited to the use of static routes for summarization. In this lesson, you will learn the role of multiple OSPF areas in solving these challenges.
Rev. 10.41
4 - 19
A Single Area
IP address space in this intranet has been hierarchically assigned to follow its physical topology. If these locations are all within the same OSPF area, routers at Locations B and C will receive the Router and Network LSAs generated due a link state change in Location A. When OSPF routers receive a link-state update which indicates there has been a change in the state of a transit network, they run the link state algorithm and build a new shortest-path tree.
Adjacent neighbors
LSAs Location A address range: 10.1.0.0/16 Location C address range: 10.3.0.0/16 Location B address range: 10.2.0.0/16
Rev. 10.41
4 - 20
Area 0.0.0.3
Area 0.0.0.3
Rev. 10.41
4 - 21
Area 0.0.0.3
ABR
Router and Network LSAs flow over adjacencies within the area
Rev. 10.41
4 - 22
Area 0.0.0.0 Summary LSAs from Area 0.0.0.2 flow through the backbone into all other non-backbone areas. Area 0.0.0.3
ABR
Area 0.0.0.1
ABR
ABR
Area 0.0.0.2
Area 0.0.0.0 Summary LSAs from Area 0.0.0.2 flow through the backbone into all other non-backbone areas. Area 0.0.0.3
ABR
Area 0.0.0.1
ABR
ABR
Area 0.0.0.2
Rev. 10.41
4 - 23
Area 0.0.0.0
Area 0.0.0.1
Rev. 10.41
4 - 24
Area 0.0.0.0
Router ID: 10.1.0.32 A Area 0 0 0 0. interface: 0.0.0.0 i t f Int. e2: 10.0.64.1/24 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.32/32 Int. e1: 10.1.128.1/24 Stub network 10.1.128.0/24 Stub network 10.1.0.32/32 0 03 Router ID: 10.1.0.34 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.34/32 Int. e2: 10.1.130.1/24 Stub network 10.1.130.0/24 Stub network 10.1.0.34/32
Router ID: 10.1.0.33 A Area 0 0 0 0. interface: 0.0.0.0 i t f Int. e2: 10.0.64.2/24 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.33/32 Int. e1: 10.1.129.1/24 Stub network 10.1.129.0/24 Stub network 10.1.0.33/32 Router ID: 10.1.0.35 0 03 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.35/32 Int. e2: 10.1.131.1/24 Stub network 10.1.131.0/24 Stub network 10.1.0.35/32
Area 0.0.0.1
Rev. 10.41
4 - 25
Area 0.0.0.0
Router ID: 10.1.0.32 A Area 0 0 0 0. interface: 0.0.0.0 i t f Int. e2: 10.0.64.1/24 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.32/32 Int. e1: 10.1.128.1/24 Stub network 10.1.128.0/24 Stub network 10.1.0.32/32
Router ID: 10.1.0.33 A Area 0 0 0 0. interface: 0.0.0.0 i t f Int. e2: 10.0.64.2/24 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.33/32 Int. e1: 10.1.129.1/24 Stub network 10.1.129.0/24 Stub network 10.1.0.33/32 Router ID: 10.1.0.35 0 03 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.35/32 Int. e2: 10.1.131.1/24 Stub network 10.1.131.0/24 Stub network 10.1.0.35/32
0 03 Router ID: 10.1.0.34 0x80000000 Area 0.0.0.1 interfaces: 0x80000000 Int. s1: unnumbered Int. s2: unnumbered 0x80000000 Loop 0: 10.1.0.34/32 0x80000000 Int. e2: 10.1.130.1/24 0x80000000 Stub network 0x80000000 10.1.130.0/24 0x80000000 Stub network 0x80000000 10.1.0.34/32
Area 0.0.0.1
Area 0.0.0.0
Router ID: 10.1.0.32 A Area 0 0 0 0. interface: 0.0.0.0 i t f Int. e2: 10.0.64.1/24 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.32/32 Int. e1: 10.1.128.1/24 Stub network 10.1.128.0/24 Stub network 10.1.0.32/32 0 03 Router ID: 10.1.0.34 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.34/32 Int. e2: 10.1.130.1/24 Stub network 10.1.130.0/24 Stub network 10.1.0.34/32
Router ID: 10.1.0.33 A Area 0 0 0 0. interface: 0.0.0.0 i t f Int. e2: 10.0.64.2/24 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.33/32 Int. e1: 10.1.129.1/24 Stub network 10.1.129.0/24 Stub network 10.1.0.33/32 Router ID: 10.1.0.35 0 03 Area 0.0.0.1 interfaces: Int. s1: unnumbered Int. s2: unnumbered Loop 0: 10.1.0.35/32 Int. e2: 10.1.131.1/24 Stub network 10.1.131.0/24 Stub network 10.1.0.35/32
Area 0.0.0.1
Rev. 10.41
4 - 26
Internet
Area 0 (Backbone) address dd range: 10.0.0.0/16
Rev. 10.41
4 - 27
Internet ASBR
ASBR
Area 1 address range: 10.1.0.0/16 RIP domain 172.16.0.0/16
Internet
ASBR
Traffic destined for the RIP domain travels through this area. Area 0.0.0.3 (Normal)
ASBR
The ABR for Area 3 floods the AS External LSAs over adjacencies into Area 3. ABRs for the stub areas (1 and 2) do not flood AS External LSAs into these areas. Instead, each originates a Type 3 Summary LSA that advertises the default route (0.0.0.0/0) and floods it to adjacent neighbors.
Rev. 10.41
4 - 28
Internet
ASBR
This technique minimizes unnecessary information in the link-state database and route tables bl of f OSPF routers internal l to the h stub area. In most implementations, ABRs can be configured to withhold advertisements of address space in other areas (Type 3 Summary LSAs), so that the default route represents all destinations outside the area.
Internet
ASBR
ASBR
Rev. 10.41
4 - 29
Internet
ABR
Module 4 Summary
This module described the operation of the OSPF routing protocol, and identified some of the terms associated with it. Topics included: The content and scope of various types of OSPF messages, and the procedures OSPF routers follow when they y receive such messages g The responsibilities associated with various OSPF router roles The effect that area type has on the advertisement of non-OSPF route information
Rev. 10.41
4 - 30
IP Multicast Protocols
Lesson 1 Introduction: 1
A server sending video traffic to specific receivers over IP networks has a choice among communication methods. Each method produces a unique result.
Unicast An individual copy of each video frame is sent to each receiver.
10.4.110.145/24 10.4.110.150/24
10.4.32.50/24
/ 10.4.10.10/24
Rev. 10.41
5-1
IP Multicast Protocols
Lesson 1 Introduction: 2
A server sending video traffic to specific receivers over IP networks has a choice among communication methods. Each method produces a unique result.
Unicast Broadcast An individual copy of each video frame is sent to each receiver. A single copy of each video frame is sent to the all hosts broadcast address.
10.4.110.145/24 10.4.110.150/24
10.4.32.50/24
The layer 2 switch floods broadcast traffic over all links potentially links, overwhelming some hosts with unwanted traffic.
10.4.10.50/24
/ 10.4.10.10/24
Lesson 1 Introduction: 3
A server sending video traffic to specific receivers over IP networks has a choice among communication methods. Each method produces a unique result.
Unicast Broadcast Multicast An individual copy of each video frame is sent to each receiver. A single copy of each video frame is sent to the all hosts broadcast address. A single copy of each video frame is sent to an IP multicast address.
10.4.110.145/24 10.4.110.150/24
10.4.32.50/24
Multicast combines the benefits of the other methods, while eliminating their disadvantages.
Layer 2 and Layer 3 devices, when configured to support IP multicast, will forward the traffic only y toward w receivers. v
/ 10.4.10.10/24
10.4.10.50/24
Rev. 10.41
5-2
IP Multicast Protocols
Multicast Addresses
Class D 224-239
Routers and switches recognize multicast traffic by the range of the first octet in its destination IP address. IP Multicast traffic uses the Class D address range: 224.0.0.0 239.255.255.255 Addresses between 224.0.0.0 and 224.0.1.255 are reserved for protocol control. For example: OSPF uses addresses 224.0.0.5 and 224.0.0.6 Network Time Protocol uses 224.0.1.1 The address range used by global content providers is between 224.0.2.0 and 233.255.255.255. Addresses in the highest g p portion of the range g are reserved for p private use within an enterprise: 239.0.0.0 239.255.255.255
Decimal
224.0.0.5
The first 24 bits are always 0x01005e The last 24 bits are composed of the last 23 bits of the IP multicast address, padded with a zero in the most significant position
Binary Hexadecimal
01005e - 00 00 05
1000 0000 0000 0000 0111 1010 Ethernet stations transmit the bits in each octet in reverse order. The first transmitted bit has the value 1, which indicates broadcast. The first transmitted bit of all unicast MAC addresses has the value 0.
Rev. 10.41
5-3
IP Multicast Protocols
IGMP
IGMP
IGMP
PIM
IGMP
IGMP
IGMP
IGMP
PIM
IGMP
Group members
Source
Rev. 10.41
5-4
IP Multicast Protocols
IGMP Querier
IGMP hosts
.11 .12 .13 .14 .11 .12 .13 .14
Network 10.1.4.0/24
Network 10.1.8.0/24
Int. 1: 10.1.4.1/24
Int. 2: 10.1.8.1/24
Network 10.1.4.0/24
Network 10.1.8.0/24
Rev. 10.41
5-5
IP Multicast Protocols
This is a type of Host Membership Request which is known as a General Query. The default interval between General Queries is 125 seconds.
There are several ways in which a multicast client application may obtain the appropriate group address, including: Hard-code the multicast address Prompt p the user to p provide the address Dynamically obtain the address from a server
Int. 1: 10.1.4.1/24
Int. 2: 10.1.8.1/24
.11
.12
.13
.14
A set of hosts, routers, and/or switches that send or receive multicast data streams to or from the same source(s).
.11
.12
.13
.14
Network 10.1.4.0/24
Network 10.1.8.0/24
Rev. 10.41
5-6
IP Multicast Protocols
The IGMP host uses this message to signal its intent to receive a specific multicast stream.
10.1.16.128/24
.11
.12
.13
.14
.11
.12
.13
.14
Network 10.1.4.0/24
Network 10.1.8.0/24
Rev. 10.41
5-7
IP Multicast Protocols
IGMP Snooping
In an environment where Layer 2 and Layer 3 forwarding functionality is performed by separate devices, successful multicast support requires that Layer 2 switches also be IGMP-aware. If the Layer 2 switch is not IGMP aware, it floods the multicast traffic over all ports. If the Layer 2 switch supports IGMP snooping, its initial behavior is the same as a switch without IGMP support. The h switch h eventually ll stops flooding fl d on nonmember ports based on detection of Membership Reports sent by group members in response to Membership Requests. IGMP-snooping switches respond to additional membership reports by forwarding the traffic toward group members.
Querier
Int. 2: 10.1.8.1/24
Int. 1: 10.1.4.1/24
Group members
.11
.12
.13
.14
.11
.12
.13
.14
Network 10.1.4.0/24
Network 10.1.8.0/24
Rev. 10.41
5-8
IP Multicast Protocols
Lesson 2 Introduction
Routers use multicast routing protocols to create a loop-free path for IP multicast traffic. End stations use IGMP to join one or more multicast groups. Downstream group presence requires routers to obtain the requested traffic from an upstream source, and forward it onto networks containing group members. Routers are nodes in the tree. The source node is the router connected to the host sending the multicast traffic. Leaf nodes with group presence join the tree by sending messages to upstream neighbors. Intermediate nodes with downstream neighbors send messages upstream to join the tree. Nodes without group presence or downstream neighbors are not part of the distribution tree.
Source
Group members
Group members
Group members
Routers define a shared tree that can carry traffic for multiple groups.
Rev. 10.41
5-9
IP Multicast Protocols
Refer to next page to view the Hello message Router 1 sends over this link.
2 4
2 4
2 3 1 3 1
PIM routers use Hello messages to discover neighbors and negotiate parameters for their relationship. The Holdtime parameter states the amount of time the neighbor should consider this routers state to be valid.
Rev. 10.41
5 - 10
IP Multicast Protocols
2 4
2 4
2 3 1 3 1
The metric in this table corresponds with the metric associated with the source network in the IP route table.
10.1.64.1
Rev. 10.41
5 - 11
IP Multicast Protocols
IP Route Table: Router 1 Destination ------------10.1.4.0/24 10.1.5.0/24 10.1.6.0/24 10.1.7.0/24 10.1.64.0/24 10 1 65 0/24 10.1.65.0/24 10.1.66.0/24 10.1.67.0/24 10.1.68.0/24 Gateway -----------10.1.64.2 10.1.65.2 10.1.68.2 Type ----------connected ospf ospf ospf connected connected t d ospf ospf connected Metric -------1 109 110 110 1 1 19 19 1 Distance -------0 110 110 110 0 0 110 110 0
Router 1s upstream PIM neighbor is 10.1.64.2, which is its next hop to reach the source network for this multicast group. This routers upstream interface, or reverse path interface is 10.1.64.1.
10.1.64.2 10.1.64.2
IP Route Table: Router 3 Destination ------------10.1.4.0/24 10.1.5.0/24 10.1.6.0/24 10.1.7.0/24 10.1.64.0/24 10 1 65 0/24 10.1.65.0/24 10.1.66.0/24 10.1.67.0/24 10.1.68.0/24 Gateway -----------10.1.65.1 10.1.67.1 10.1.65.1 10.1.65.1 10.1.65.1 10.1.65.1 Type ----------ospf ospf connected ospf ospf connected ospf connected ospf Metric -------109 110 1 119 18 1 29 1 19 Distance -------110 110 0 110 110 0 110 0 110
This routers upstream PIM neighbor is 10.1.67.1. Its reverse path interface is 10.1.67.2.
Rev. 10.41
5 - 12
IP Multicast Protocols
IP Route Table: Router 4 Destination ------------10.1.4.0/24 10.1.5.0/24 10.1.6.0/24 10.1.7.0/24 10.1.64.0/24 10 1 65 0/24 10.1.65.0/24 10.1.66.0/24 10.1.67.0/24 10.1.68.0/24 Gateway -----------10.1.66.1 10.1.66.1 10.1.68.1 10.1.66.1 10 1 68 1 10.1.68.1 10.1.66.1 Type ----------ospf ospf ospf connected ospf ospf f connected ospf connected Metric -------110 109 119 1 18 19 29 19 19 Distance -------110 110 110 0 110 110 110 0 110
This routers upstream PIM neighbor is 10.1.66.1. Its reverse path interface is 10.1.66.2.
Source: 10.1.5.37/24
2 4
2 3 1 3 1
Router 4: Int 1: 10.1.7.1/24 Int 2: 10.1.66.2/24 Int 3: 10.1.68.2/24 Reverse Path interface Filtered interface
Rev. 10.41
5 - 13
IP Multicast Protocols
Router 1 floods the traffic it receives through its interface to the network it shares with Router 2. Routers 3 and 4 flood the multicast traffic they receive through their reverse path interfaces. The routers discard traffic they receive through filtered interfaces. HP networking E-series routing switches that implement Data-Driven IGMP will forward the traffic on to user networks only after IGMP hosts have joined the multicast group.
Router 1: Int 1: 10.1.4.1/24 Int 2: 10.1.64.1/24 Int 10.1.65.1/24 I 3: 3 10 1 65 1/24 Int 4: 10.1.68.1/24
2 4
Router 2: Int 1: 10.1.5.1/24 Int 2: 10.1.64.2/24 Int 10.1.66.1/24 I 3: 3 10 1 66 1/24 Int 4: 10.1.67.1/24
2 3 1 3 1
2 4
Router 2: Int 10.1.5.1/24 I 1: 1 10 1 5 1/24 Int 2: 10.1.64.2/24 Int 3: 10.1.66.1/24 Int 4: 10.1.67.1/24
2 3 1 3 1
Rev. 10.41
5 - 14
IP Multicast Protocols
.11
.12
.13
.14
2 4
In its role as IGMP Querier, each router maintains tables that determine whether its user VLANs contain group members members. Router 1 remains a part of the distribution tree for this multicast group due to downstream group presence.
No group members
No group members
Based on lack of group presence, Routers 3 and 4 each send a PIM Prune message to upstream neighbors.
The Prune message is sent to the PIM reserved multicast address address. This message format is used for the Prune message as well as a Join message used by PIM Sparse. On a multi-access network, this PIM router may have multiple upstream neighbors. The message specifies the upstream neighbor to which this message applies. This distribution tree carries the data stream for a single multicast group. However, this message could include information relating to multiple groups. The message specifies the multicast source whose data stream should be pruned.
Rev. 10.41
5 - 15
IP Multicast Protocols
.11
.12
.13
.14
Router 2 maintains the prune state for its downstream neighbors, Router 3 and Router 4, until they send a message changing the state. When Router 3s IGMP tables indicate group presence, it sends a PIM Graft message upstream.
Router 1: Int 10.1.4.1/24 I t 1: 1 10 1 4 1/24 Int 2: 10.1.64.1/24 Int 3: 10.1.65.1/24 Int 4: 10.1.68.1/24
1 4
2 4
Router 2: Int 10.1.5.1/24 I t 1: 1 10 1 5 1/24 Int 2: 10.1.64.2/24 Int 3: 10.1.66.1/24 Int 4: 10.1.67.1/24
.11
.12
.13
.14
No group members
The target of a PIM Graft message is a specific neighbor instead of the PIM reserved multicast address. dd
A PIM Graft message sets the Join field at 1 and the Prune field at 0. Like the Prune message, it specifies the distribution trees source and group addresses.
Rev. 10.41
5 - 16
IP Multicast Protocols
.11
.12
.13
.14
Router 2 maintains the prune state for its downstream neighbors, Router 3 and Router 4, until they send a message changing the state. When Router 3s IGMP tables indicate group presence, it sends a PIM Graft message upstream. Router 2 acknowledges th G the Graft ft message.
IGMP Host Membership Report
Router 1: Int 10.1.4.1/24 I t 1: 1 10 1 4 1/24 Int 2: 10.1.64.1/24 Int 3: 10.1.65.1/24 Int 4: 10.1.68.1/24 3
2 4
Router 2: Int 10.1.5.1/24 I t 1: 1 10 1 5 1/24 Int 2: 10.1.64.2/24 Int 3: 10.1.66.1/24 Int 4: 10.1.67.1/24
.11
.12
.13
.14
No group members
Ethernet header: Dest: <Router_3_MAC> Source: <Router_2_MAC> Type: IP (0x0800) IP datagram header: Protocol: PIM (0x67) (Decimal: 103) Source: 10.1.67.1 Destination: 10.1.67.2 Protocol Independent Multicast header: Version: 2 Type: Graft-Ack (7) PIM parameters: Groups: 0
The e router ou e receiving ece v g a PIM MG Graft a message essage from o a downstream neighbor sends a Graft Acknowledgment before sending the data stream.
Rev. 10.41
5 - 17
IP Multicast Protocols
.11
.12
.13
.14
Router 1 and Router 3 remain on the distribution tree as long as each has at least one group member on its user network.
2 4
2 3 1 3 1
.11
.12
.13
.14
No group members
.11
.12
.13
.14
Router 1 and Router 3 remain on the distribution tree as long as each has at least one group member on its user network. When the last member on Router 1s user network leaves the group, the router prunes itself from the tree.
2 3 1 3 1
.11
.12
.13
.14
No group members
Rev. 10.41
5 - 18
IP Multicast Protocols
R7
PIM Join
R1
R2
R5
R6
PIM-SM Domain
BSR for the domain
R7
RP for 239.192.0.0/10
RP for 239.64.0.0/10
R1
.1
R2
R5
10.1.5.0/24
.2
PIM Join
R3
R4
R6
Rev. 10.41
5 - 19
IP Multicast Protocols
BSR Candidate
10.1.66.0/24 .2
R1
.1
R2
R5
.1
BSR Candidate
10.1.5.0/24 .2
10.1.12.0/24 .2
R3
R4
R6
Ethernet header: Dest: 01:00:5e:00:00:0d Source: <R7_MAC> Type: IP (0x0800) IP datagram header: Protocol: PIM (0x67) (Decimal: 103) Source: 10.1.64.1 Destination: 224.0.0.13
Bootstrap messages are sent to the All PIM Routers multicast group. Each PIM router changes the packets Layer 2 and Layer 3 addresses as it forwards the Bootstrap message.
Protocol Independent Multicast header: Version: 2 Type: Bootstrap (4) PIM parameters: t These h values l determine d which h h BSR S Candidate C dd will ll become the active BSR. The original BSR Hash mask len: 30 advertisement remains unchanged as the BSR priority: 10 Bootstrap message PIM is propagated throughout BSR: 10.1.66.1
the domain.
Rev. 10.41
5 - 20
IP Multicast Protocols
.1 .1 .1
R7
10.1.64.0/24 .2
10.1.65.0/24 .2
10.1.66.0/24 .2
BSR Candidate
R1
.1
R2
R5
10.1.5.0/24
R3
R4
R6
RP Candidates send their advertisements directly to the elected BSR, and not the PIM multicast group.
The PIM portion of the packet lists the multicast address ranges associated with this RP.
Rev. 10.41
5 - 21
IP Multicast Protocols
.1 .1 .1 10.1.66.0/24 .2
10.1.64.0/24 .2
10.1.65.0/24 .2 .1
R1
.1
R2
10.1.4.0/24 10.1.5.0/24 .2
RP for 224.0.0.0/4
R5
R3
.2
R4
R6
The BSR originates a copy of the Bootstrap message for each of its interfaces that support PIM neighbors. i hb It is i sent tt to th the multicast lti t address dd that includes all PIM routers.
Protocol Independent Multicast header: Type: Bootstrap (4) PIM parameters: Hash mask len: 30 BSR priority: 10 BSR: 10.1.65.1 Group 0: 224 224.0.0.0/4 0 0 0/4 RP count: 1 RP 0: 10.1.65.2 This message includes the RP-to-group mappings from all RP Candidate Priority: 192 Advertisements. Its contents are not Group 1: 224.0.0.0/4 limited to the active RP. RP count: 1 RP 0: 10.1.66.2 Priority: 255
Rev. 10.41
5 - 22
IP Multicast Protocols
Sharing RP Responsibilities
Individual RPs can be configured to act as the root of a tree that supports a subset of multicast addresses. This is often done to enable load sharing. Server 2: In the example, R2 and R5 have each been configured as Candidate RPs for only a portion of the multicast address space. R7 is configured as an RP Candidate for the entire multicast address space. As each multicast data transmission begins, the Designated Router (DR) for the source network consults its PIM tables and learns the identity of each RP RP. The DR encapsulates the traffic in an outer packet that specifies the unicast IP address of the RP. The RP decapsulates the packets and sends them downstream.
Server 1: S: 10.1.5.17 G: 239.64.11.37
.1 .1 .1
R7
RP Candidate: 224.0.0.0/4
S: 10.1.5.3 G: 239.192.12.42
10.1.64.0/24 .2
10.1.65.0/24 .2 .1
10.1.66.0/24 .2
R1
.1 10.1.5.0/24
10.1.4.0/24
RP for R2 239.192.0.0/10
R5
RP for 239.64.0.0/10
.2
R3
.2
R4
R6
10.1.10.0/24
10.1.6.0/24
.1 .1 .1
R7
RP Candidate: 224.0.0.0/4
10.1.64.0/24 10 1 64 0/24 .2
10 1 65 0/24 10.1.65.0/24 .2 .1
10.1.66.0/24 10 1 66 0/24 .2
R1
.1 10.1.5.0/24
10.1.4.0/24
RP for R2 239.192.0.0/10
R5
RP for 239.64.0.0/10
.2
R3
.2
R4
R6
10 1 10 0/24 10.1.10.0/24
10 1 6 0/24 10.1.6.0/24
Rev. 10.41
5 - 23
IP Multicast Protocols
Module 5 Summary
This module described the operation of three protocols that enable transmission of multicast traffic within an intranet. In this module you learned: The format of IGMP messages, and how network devices use IGMP information to forward multicast traffic to g group p members The behavior of routers using PIM Dense mode, including the messages they use to become neighbors, and join and leave the distribution tree The similarities between PIM Dense and Sparse modes How the Rendezvous Point and Bootstrap Routers distribute information to other routers that use PIM-Sparse
Rev. 10.41
5 - 24
Lesson 1 Introduction
Bandwidth is typically provisioned based on a calculated average percentage of utilization per client computer. Adequate provisioning is the first step in providing QoS for time-sensitive traffic. For example, an access switch supporting 20 gigabit clients at 5% utilization would require a 1-Gbps uplink. Clients may periodically burst to their maximum bandwidth. bandwidth The switch uses packet buffering to maintain forwarding in the face of higher traffic volumes. If the congestion continues for long enough, some packets will be delayed or even discarded. Because congestion has a more negative effect on time-sensitive traffic than some other types, one goal of QoS is to control which y to be discarded when congestion g occurs. traffic is least likely
1- Gbps uplink
Rev. 10.41
6-1
Host2 Application
Among other items, the hosts negotiate a window size (rollover text: limits the how many packets can be in transit and unacknowledged) that hosts use to slow down their transmission when they detect congestion. An acknowledgement timer defines the length of time each host will wait for acknowledgements from the other.
Transport (TCP)
Host1
Application
Host2
Application
Transport 4 (TCP) 3 2 1
The transport layer creates sequentially numbered segments and sends them to the Network layer.
Transport (TCP)
The message may be further segmented at Network and Data Link Layers as it is encapsulated and transmitted.
Rev. 10.41
6-2
Host1
Application
Host2
If Host1 does not receive acknowledgement of packets 3 and 4 before its timer expires, it retransmits them. Host2 acknowledges receipt of packets 1 and 2 by including the highest received segment number in the TCP header of packets it sends to Host1.
Application
Transport 4 (TCP) 3 2 1
Transport (TCP)
If the number of delayed or retransmitted packets is outside a predefined tolerance level, the hosts negotiate a smaller window size, effectively backing down the transmission speed.
Host1
Application
Host2
Application
Transport (UDP)
Transport (UDP)
Physical
Rev. 10.41
6-3
Rev. 10.41
6-4
Edge ports
Uplink
UDP data traffic ff Voice traffic TCP data traffic Ingress ports
4 3 2 1
Egress port
Rev. 10.41
6-5
UDP data traffic ff Voice traffic TCP data traffic Ingress ports Egress port queues
4 3 2 1
Egress port
Most IP phones and many other devices sending time-sensitive traffic use Layer 2 markers to indicate priority. Devices may also request priority handling by marking the Type of Service field in the IPv4 datagram header.
Rev. 10.41
6-6
Priority Mechanisms: 1
Recognition of time-sensitive traffic and forwarding it ahead of normal traffic are two of the three formalized steps involved in prioritization. 1. Classification The switch reads the packet header to learn its priority and assigns it to a traffic class, which is also known as internal forwarding priority. 2 2. Marking If the switch will need to create a new header for the packet, it modifies the header to reflect the appropriate priority value. Packets are marked for the benefit of other QoS-capable devices which may handle the packet downstream. 3. Scheduling The switch places the packet in the queue associated with its traffic class. The 802.1Q standard specifies relative priority of the traffic classes. Some switches require QoS support to be manually enabled. ProVision ASIC switches are able to classify, mark, and schedule traffic as soon as you have configured VLANs.
Priority Mechanisms: 2
802.1p value Binary 111 110 101 100 011 010 001 000 Decimal 7 6 5 4 3 0 2 1 Traffic class (highest) 7 6 5 4 3 (normal) 0 2 (lowest) 1 When mapped to 8 queues (highest) 8 7 6 5 4 (normal) 3 2 (lowest) 1 (lowest) 1 (normal) 2 (normal) 1 (medium) 3 When mapped to 4 queues (highest) 4 When mapped to 2 queues (high) 2
Rev. 10.41
6-7
The switch does not need to mark the header because the packet is being forwarded at Layer 2. Specifically, the destination port is in the same VLAN as the source port. Note that the priority marker (110) remains intact in the header after the packet has been forwarded.
Priority (binary) VLAN ID (represented in decimal) [MAC header] ... 110 ... 130... [IP header]
802.1Q tag
Layer 2 switch
Priority (binary) VLAN ID (represented in decimal) [MAC header] ... 110 ... 130... [IP header]
802.1Q tag
Priority (binary)
VLAN ID (decimal)
Classify: y Assign g the p packet to traffic class 6 Mark: Record binary value 6 in the 802.1Q tag of the new header the switch creates for the routed packet. Schedule: Place the packet in the queue associated with traffic class 6.
Layer 3 switch
Priority (binary) VLAN ID (represented ) in decimal) [MAC header] ... 110 ... 130... [IP header]
802.1Q tag
Layer 2 switch
Rev. 10.41
6-8
Layer 3 switch
In the absence of a specific policy, this Layer 3 switch will forward the packet with normal priority whether it is forwarded over tagged or untagged links
Priority (binary) VLAN ID (represented in decimal) [MAC header] ... 000 ... 24... [IP header]
802.1Q tag
Layer 2 switch
This port is an untagged member of VLAN 24
Version (4) HL (4 bits) Type of Service (8 bits) Identifier (16 bits) Time to Live (8 bits) Protocol (8 bits) Flags (3) Source Address (32 bits)
Total Length (16 bits) Fragment Offset (13 bits) Header Checksum (16 bits)
Rev. 10.41
6-9
A packet decoder would display the hexadecimal value of the entire TOS field: A0.
Only 13 of the 64 possible values are standardized as DiffServ CodePoints (DSCP). Expedited Forwarding (EF) is assigned the highest user-defined value using the DiffServ definition: 46
Rev. 10.41
6 - 10
Lesson 2 Introduction
LLDP is a useful protocol that enables switches to dynamically learn the identity and other characteristics of their neighbors. An LLDP extension for Media Endpoint Devices (LLDP-MED) enables phones and other endpoints to report their requirements and capabilities to a connected switch. In this lesson you will learn some of the benefits of LLDP-MED.
LLDP
LLDP
LLDP-MED
To wiring closet
Rev. 10.41
6 - 11
Transmit and receive operations are independent The switch creates a unique message to be sent over each link Received LLDP messages are not forwarded over other links LLDP messages can be forwarded over links blocked by Spanning Tree
LLDP advertisements are sent to a Layer 2 multicast address. Each advertisement a series of TLVs, each of which provides a single type of information.
MIB Port A1 Device Switch1 Type Switch Info xxxx
A1
Switch2
Switch1
50
Rev. 10.41
6 - 12
Module 6 Summary
This module described some of the technologies used to provide priorities for traffic generated by time-sensitive applications. Topics included: Classification and scheduling strategies employed by switches Marking Priority within the IEEE 802.1Q tag and IP datagram header
Rev. 10.41
6 - 13
subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.