HP Switching and Routing Technologies: Web-Based Training Course Companion

HP Switching and Routing Technologies
Web-based Training Course Companion

Version 10.41
 Copyright 2010 Hewlett-Packard Development Company, L.P.
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
HP Switching and Routing Technologies 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
Converged Applications Drive Infrastructure Enhancements

Organizations typically implement converged solutions to lower the costs of services like voice telephony
and multimedia conferences, training, and presentations. At the same time, converged solutions enable
greater flexibility by integrating services formerly carried on separate networks.
IP Telephony Video conferencing and Video surveillance

distance learning
While these integrated applications enhance user productivity, they place additional requirements on the
iinfrastructure
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

Convergence Requires High Availability 1

High availability is crucial in converged networks. Because all communication systems are concentrated in a single
infrastructure, network outages would be particularly disruptive.
HP networking products can enhance resilience on many levels by supporting:
• The Virtual Router Redundancy Protocol, which enables a standby router to automatically resume forwarding traffic if
the p
primaryy default g
gatewayy fails
• The Spanning Tree Protocol, which blocks redundant switched links until a failure elsewhere may cause them to
transition to the forwarding state
• Multiple Spanning Tree, which defines separate active paths per instance, enabling utilization of redundant links and
devices that would otherwise remain inactive
Instance 1 Primary default gateway Instance 1 Backup default gateway

Instance 2 Backup default gateway Instance 2 Primary default gateway
Links that are active

for Instance 1
Links that are active

for Instance 2
Hosts in VLANs Hosts in VLANs Hosts in VLANs Hosts in VLANs
mapped to Instance 1 mapped to Instance 2 mapped to Instance 1 mapped to Instance 2
Convergence Requires High Availability 2
Connections to other resources and client systems

Redundant routed links between distribution and core layer switches may
be utilized if you select a routing protocol, such as OSPF, that supports
Equal-Cost Multipath (ECMP).
C
Core layer
l
If both core switches in the example have access to the same resources, the
switches
distribution layer switches can forward traffic over both equal-cost paths.
Distribution layer
y
switches
Rev. 10.41 1-2

Redundant Components in Network Devices

You can increase the availability of network devices by providing redundant hardware components within distribution
and/or core switches.
The HP E8200 switch series can be configured to provide resilience for hardware components.
• Redundant management module – failover to hot standby module
• Resilient switch fabric modules – system can tolerate the loss of one module
• Redundant, hot-swappable power supplies – providing N+1 power protection –

are accessible from the rear of the unit
Redundant
management
modules
Redundant
power
supplies Resilient fabric
modules
Real-time Traffic Requires Predictability
Real-time traffic, such as web video and VoIP, is far more sensitive to network congestion than typical IP
data traffic. To be successful, a converged network must exhibit predictable behavior under all
circumstances.
In this example, devices within the network cloud experience varying levels of congestion. Consequently,
some packets in the real
real-time
time data stream are delayed
delayed.
The outcome of the congestion is a variation in the interval between packet arrival, known as jitter,
which results in a choppy voice or video stream.
Network users who experience high jitter levels are likely to be dissatisfied with the performance of
voice and video applications, producing the perception that the network is not functioning properly.
Host 1 Host 2
Senders of real-time traffic Receivers expect the packets to

transmit packets at fixed arrive at the same interval.
intervals.
Rev. 10.41 1-3

IP Telephony Traffic Requires Low Delay
Traffic sent by this IP phone must reach the receiver in a timely manner. However, a certain amount of
delay is inevitable as a message is sent through the network. One-way delay is defined as the interval
between the time the first bit in a packet is sent and the time it is received.
Congestion can cause levels of delay that are unacceptable for IP telephony and video-conferencing
applications A converged infrastructure must employ measures that limit delay
applications. delay.
Phone 1 Phone 2
IP Telephony Requires Intelligence at the Edge
To minimize the effects of congestion on real-time traffic, a converged infrastructure requires intelligent
devices at the edge and core layers.
An HP networking edge switch and an IP phone negotiate parameters using a standardized mechanism
known as Link Layer Discovery Protocol for Media Endpoint Devices (LLDP-MED).
LLDP-MED
• The phone identifies itself as a VOIP • The switch dynamically places the IP
device,, p
providing
g manufacturer and phone in appropriate
p pp p VLAN and
other inventory information reports the VLAN ID to the phone.
• The phone adds appropriate • Switch applies policies that will ensure
802.1Q tag and priority settings to voice quality.
the traffic it generates.
You will learn more about LLDP-MED and other topics relating to Quality of Service in Module 6.
Rev. 10.41 1-4

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

HP Switching and Routing Technologies Providing Redundant Links and Gateways
Module 2: Providing Redundant Links and Gateways

Objectives
Each host’s default gateway is crucial in enabling its communication with remote resources.
This module will describe the operation of Version 2 of the Virtual Router Redundancy Protocol
(VRRP v2) and its interaction with the Spanning Tree Protocol.
After completing
p g this module,, yyou will be able to:
• Describe the interactions among network devices that support VRRP v2
• Describe how multiple spanning tree instances enable two layer 3 switches to share default
gateway responsibilities
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 Server Router_x Host1 Server Payload
with every router hop. Dest. Source Source Dest.
MAC header IP header 10 119215
10.1.192.15
All destinations
outside
While the Layer 3 header on the packets from Host1 10.1.10.0/24
to the Server contains the actual source and
destination IP addresses, the Layer 2 header Router1
indicates that traffic is destined for the Host1’s
default gateway, Router1.
10.1.10.1/24
Router1 Host1 Host1 Server Payload

Dest. Source Source Dest.
MAC header IP header Switch
Host 1 All IP hosts require a gateway in their

10.1.10.100/24 local address range to reach non-local
Gateway: 10.1.10.1 destinations.
Rev. 10.41 2-1

If this router, or the path between the host and the router, becomes unavailable, the
host’s 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 10 119215
10.1.192.15
The host will need to reconfigure its default gateway and

All destinations
establish new sessions. The replacement router interface outside
cannot assume forwarding responsibility for open sessions. 10.1.10.0/24
The Virtual Router Redundancy Protocol (VRRP) may

Router1
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. Router2
Switch
10.1.10.2/24
Host 1
10.1.10.100/24
Gateway: 10.1.10.1
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) Non-owner (Backup)

Actual IP address: Actual IP address:
VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24
Router1 Router1
VLAN 10 - Virtual Router ID: 1

10.1.10.1 Virtual IP address: 10.1.10.1 10.1.10.1
Switch1
VLAN 10 Host: 10.1.10.10/24
Default gateway: 10.1.10.1
Rev. 10.41 2-2

VRRP Virtual MAC Address

00:00:5e:00:01:01
In addition to a virtual IP address, a virtual MAC address is
assigned to each virtual router.
First 40 bits
The VRRP Master broadcasts a gratuitous ARP request that causes
specified in
hosts on the VLAN to create an ARP cache entry associating the
RFC 3768
virtual IP address with the virtual MAC address.
Last 8 bits =
Virtual Router ID
Owner (Master) Non-owner (Backup)

Actual IP address: Actual IP address:
VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24
Router1 Router1
VLAN 10 - Virtual Router ID: 1

10.1.10.1 Virtual IP address: 10.1.10.1 10.1.10.1
Virtual MAC: 00:00:5e:00:01:01
Switch1
VLAN 10 Host: 10.1.10.10/24
Gratuitous ARP Request
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
matching values for Source and Target IP address.
address The
message causes each host in this network to add the following
Virtual IP Address 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.
Master VLAN 10: 10.1.10.1/24 Backup VLAN 10: 10.1.10.2/24

Router1 Router1
VLAN 10 VRRP
Advertisement
Switch1
VLAN 10 Host: 10.1.10.10/24
VLAN 10 VRRP Advertisement
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) This advertisement is sent to the
Source: 10.1.10.1 Destination: 224.0.0.18 multicast address assigned to VRRP
in RFC 3768
Virtual Router Redundancy Protocol header:
Version: 2
Packet type: Advertisement (1)
Virtual Router ID: 1 This priority level indicates that the
P i it 255
Priority: originator of this message is the
Count IP Addrs: 1 owner of the Virtual IP Address.
Auth Type: No authentication (0)
Advertisement Interval: 1 (sec) A copy if this advertisement is sent
IP Address: 10.1.10.1 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: 10.1.10.1/24 (Owner) VLAN 10: 10.1.10.2/24 (Backup)

VLAN 20: 10.1.20.2/24 (Backup) VLAN 20: 10.1.20.1/24 (Owner)
Router1 Router2
VLAN 10 - VRID: 1: 10.1.10.1

10 110 1
10.1.10.1 10 110 1
10.1.10.1
Virtual MAC: 00:00:5e:00:01:01
VLAN 20 : VRID 2: 10.1.20.1

10.1.20.1 10.1.20.1
Virtual MAC: 00:00:5e:00:01:02
Switch1
VLAN 10 Host: 10.1.10.10/24 VLAN 20 Host: 10.1.20.10/24
Default gateway: 10.1.10.1 Default gateway: 10.1.20.1
VRRP Master Failover: 1

Router interfaces that are part of the same virtual router negotiate for the Master and Backup roles
based on their priority settings. The Owner has the highest possible priority (255) and will always
assume the role of Master.
In the example below, Router1 is the Master for VLAN 10, and sends VRRP advertisements over that
VLAN. Router2 is the Master for VLAN 20.
VRRP Backup
k routers llisten ffor advertisements.
d Iff the
h Master stops sending
d advertisements,
d the
h Backup
k
assumes the Master role.
VLAN 10: 10.1.10.1/24 (Master) VLAN 10: 10.1.10.2/24 (Backup)
VLAN 20: 10.1.20.2/24 (Backup) VLAN 20: 10.1.20.1/24 (Master)
Router1 Router2
Switch1
Rev. 10.41 2-5

VRRP Master Failover: 2

Router interfaces that are part of the same virtual router negotiate for the Master and Backup roles
based on their priority settings. The Owner has the highest possible priority (255) and will always
assume the role of Master.
In the example below, Router1 is the Master for VLAN 10, and sends VRRP advertisements over that
VLAN. Router2 is the Master for VLAN 20.
VRRP Backup
k routers llisten ffor advertisements.
d Iff the
h Master stops sending
d advertisements,
d the
h Backup
k
assumes the Master role.
VLAN 10: 10.1.10.2/24 (Master)
VLAN 20: 10.1.20.1/24 (Master)
Router1 Router2
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 10: 10.1.10.2/24

VLAN 20: 10.1.20.1/24 VLAN 20: 10.1.20.2/24
Bridge Priority 0 (Root) Bridge Priority 4096 (Backup Root)
Router1 Tagged Router2
10 20
10 20
10 Tagged 10
Tagged Tagged
20 10 20 20
Tagged
Switch1 Switch2
VLAN 10 Hosts: VLAN 20 Hosts: VLAN 10 Hosts: VLAN 20 Hosts:
10.1.10.0/24 10.1.20.0/24 10.1.10.0/24 10.1.20.0/24
Rev. 10.41 2-6

VRRP Advertisements and Spanning Tree

The routing switch configured as Spanning Tree Root should be configured as VRRP Owner. The Master
sends VRRP advertisements over each of link for each VLAN.
When all links are up, the direct link between Master and Backup is the primary path for VRRP
advertisements. If the path between the VRRP Master and Backup is disrupted, the Backup will assert
itself as the Master and this will prevent proper VRRP operation.
The
h edge
d switches,h Switch1
S h andd Switch2,
S h2 cannot forward
f d the
h VRRP advertisements
d toward
d the
h Backup
k
because their uplinks to the Backup are in the Spanning Tree Blocking state.
For this reason, the direct Master-Backup link must carry all of the VLANs in this domain. Should this link
become unavailable, the remaining links must carry the advertisements for all VLANs.
VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

VLAN 20: 10.1.20.1/24 VLAN 20: 10.1.20.2/24
Router1 Router2
B B
Switch1 Switch2
Gateway Load Sharing in a Single Spanning Tree: 1

In a single Spanning Tree environment, a single active path carries traffic for all configured VLANs. For
the efficiency of traffic flow, the Root of the tree should be the VRRP Master for all VLANs whose traffic is
carried by the links in the tree.
Because interfaces on Router1 serve as default gateway for both hosts, their traffic uses the same set of
links in either direction.
VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

VLAN 20: 10.1.20.1/24 VLAN 20: 10.1.20.2/24
HostB Router1 HostA HostB Payload
Router1 Router2
MAC header IP header
Router1 delivers the
Router1 HostA HostA HostB Payload packet directly to Host B.
Because Router1 is Host
A’s gateway, its MAC
address appears in the
packet’s Layer 2 header.
B B
Switch1 Switch2
Host A: Host B:
10.1.10.10/24 10.1.20.10/24
Gateway: 10.1.10.1 Gateway: 10.1.20.1
Rev. 10.41 2-7


In this load-sharing configuration, the VRRP Master for VLAN 20 does not correspond with the Spanning
Tree Root. Consequently, the uplink between Switch2 and its default gateway (Router2) is blocked by
Spanning Tree. Traffic between Host B and its default gateway must first be forwarded at Layer 2
through Router1 before reaching Router2.
Router1 forwards the packet at Layer 2 because the destination MAC address is not its own address.
VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

VLAN 20: 10.1.20.1/24 VLAN 20: 10.1.20.2/24
Router1 Router2
HostA Router2 HostB HostA Payload
Router1 forwards the packet
to Router2 at Layer 2.

B Router2 is the default gateway B
Switch1 for Host B. However, the Switch2
uplink from Switch 2 to Router
Host A: 2 is in Blocking state. Host B:
10.1.10.10/24 10.1.20.10/24
Gateway: 10.1.10.1 Gateway: 10.1.20.1

The link between Router2 and Switch1 is blocked by Switch1. However, Router2’s interface to this
network is in the Forwarding state, and this enables Router2 to forward the packet directly to Host A.
VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

VLAN 20: 10.1.20.1/24 VLAN 20: 10.1.20.2/24
Router1 Router2

Router2 forwards the packet
to Host A through Switch1.
B B
Switch1 Switch2
Host A: Host B:
10.1.10.10/24 10.1.20.10/24
Gateway: 10.1.10.1 Gateway: 10.1.20.1
Rev. 10.41 2-8

VRRP and Multiple Spanning Tree

The Multiple Spanning Tree Protocol (MSTP) enables definition of multiple spanning tree instances.
• Each Multiple Spanning Tree (MST) Instance can support a unique set of VLANs.
• Spanning Tree parameters are separately configured for each instance, enabling definition of a Root
Bridge for each instance.
g switches to share g
MSTP enables a set of routing gatewayy responsibilities
p for a set of VLANs.
MST Instance 1: VLAN 10
MST Instance 1: VLAN 10
Bridge Priority: 0 (Root) Bridge Priority: 4096 (Backup Root)
MST Instance 2: VLAN 20 MST Instance 2: VLAN 20

Bridge Priority: 4096 (Backup Root) Bridge Priority: 0 (Root)
Router1 Router2
B B
Switch1 Switch2
Host A: Host B:
10.1.10.10/24 10.1.20.10/24
Gateway: 10.1.10.1 Gateway: 10.1.20.1
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 TTree
• How the configuration of Multiple Spanning Tree instances enables routers to share gateway
responsibilities
Rev. 10.41 2-9

HP Switching and Routing Technologies 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 packet’s 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.
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 packet’s
Layer 3 information to determine which of its interfaces
leads to the destination, and creates a new Layer 2 HostB:
header for each packet it forwards
forwards. S it h2
Switch2 Network 2
Routers may pass traffic between a pair of hosts located

on directly connected networks.
• The packet’s Layer 2 header contains the MAC address RouterA

of the interface that provides default gateway service
for Network 1.
• The router removes the existing Layer 2 header and Network 3
creates a new header with HostB’s MAC address as RouterA
the destination. Switch1
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.
HostA:
Network 1
HostC:
Network 4
Rev. 10.41 3-1

Local Networks and the IP Route Table

Router interfaces are configured with an IP address and mask. When the router boots, it derives the range
of addresses on its connected networks by applying the configured mask to each interface address.
The mask 255.255.255.0 indicates that the first 24 bits of the IP address represent the network portion.
The last 8 bits represent the host portion of the address.
For each interface whose state is “up,”
p, the router p
places its network address range
g into the IP route table.
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.
R
RouterA
A
Router interface 1: Router interface 2:
IP address: 10.1.10.1/24 IP address: 10.1.20.1/24
Subnet mask: 255.255.255.0 Subnet mask: 255.255.255.0
Hosts in the range: Hosts in the range:

10.1.20.0/24 10.1.20.0/24
Router Interface Types

Routers often support a variety of interface types in addition to the port-based interfaces shown on the
previous screen. These may include:
• VLAN interfaces, which are considered “up” if at least one port member of the VLAN is active
• Loopback interfaces, which are always considered “up” because they are not bound to any physical
interfaces
VLAN 10 interface: 10.1.10.1/24

Loopback 0: 10.1.0.25
RouterA
VLAN 20 interface: 10.1.20.1/24
Switch1
Hosts in the range Hosts in the range

10.1.20.0/24 10.1.10.0/24
Rev. 10.41 3-2

Dynamic Routing Protocols

A router can learn about the existence of remote networks through dynamic interaction with neighboring
routers.
Routers that share information must follow a common protocol,
which is set of rules for exchanging routing information.
VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24 RouterA
gp
Routing protocols mayy specify:
p y VLAN 100: 10
10.1.100.1/24
1 100 1/24
Loop 0: 10.1.0.25/32
• Procedures for establishing neighbor relationships
10.1.10.0/24
• The format of messages exchanged between neighbors 10.1.20.0/24
10.1.0.25/32
• Conditions or events that require the routers to send
updated information
10.1.30.0/24
10.1.40.0/24
10.1.0.26/32
VLAN 30: 10.1.30.1/24 RouterB

VLAN 40: 10.1.40.1/24
VLAN 100: 10.1.100.2/24
Loop 0: 10.1.0.26/32
Static Route Configuration

Routers can also learn about remote networks by static configuration. In this example, two VLANs are
directly connected to each router.
The routers are connected by the network 10.1.100.0/24.
An administrator specifies the remote address range and the next hop toward the destination.
VLAN 10: 10
10.1.10.1/24
1 10 1/24
RouterA
ip route 10.1.30.0/24 10.1.100.2 1 VLAN 20: 10.1.20.1/24
VLAN 100: 10.1.100.1/24
Loop 0: 10.1.0.25/32
This command, issued at the CLI of RouterA, provides
information the router will use to forward traffic toward the VLAN 100:
destination network 10.1.30.0/24 10.1.100.1/24
This command,
Th d issued
d at the
h CLI off RouterB,
R B provides
d
information the router will use to forward traffic toward
the destination network 10.1.10.0/24
VLAN 100:
ip route 10.1.10.0/24 10.1.100.1 1 10.1.100.2/24
VLAN 30: 10.1.30.1/24 RouterB
VLAN 40: 10.1.40.1/24
VLAN 100: 10.1.100.2/24
Network topology, including Internet and intranet connectivity, Loop 0: 10.1.0.26/32
determine appropriate methods for each situation.
Rev. 10.41 3-3

Routing Protocol Categories

Dynamic interaction between routers falls into two basic categories.
1. Interior Gateway Protocols (IGP) facilitate the OSPF

exchange of information among routers under
AS 100
the same organizational control; that is, within ABC Corp - Europe
the same Autonomous System (AS).
Common examples of standard IGPs include:
BGP
• Routing Information Protocol (RIP)
• Open Shortest Path First (OSPF)
2. Exterior Gateway Protocols (EGP) facilitate the AS 200 BGP/
ABC Corp IS-IS
exchange of route information among routers
in different Autonomous Systems.
• Border Gateway Protocol version 4
(BGP4) isi the
h current standard
d d EGP BGP
for Internet connectivity
• Internet Service Providers often use an IGP,
such as IS-IS, within their own networks to RIP
enable connectivity among BGP routers. AS 300
ABC Corp - Japan
Standard Interior Gateway Protocols: 1

Standard Interior Gateway Protocols include:
Network 1 – cost 1
Network 3
1. Routing Information Protocol (RIP) is a distance Network 2 – cost 1
vector protocol.
Each router sends periodic updates, based on
its own route table.
table Networkk 1 – cost 2
Information about remote networks is passed Network 2 – cost 2
from router to router, with costs incrementing Network 3 – cost 1
with each hop.
Network 4
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

Standard Interior Gateway Protocols: 2

Network 3
Standard Interior Gateway Protocols include:
1. Routing Information Protocol (RIP) is a distance R1 advertisement

vector protocol.
Each router sends periodic updates, based on
its own route table.
table R1 advertisement
Information about remote networks is passed

from router to router, with costs incrementing Network 4
with each hop.
Link-state database
2. Open Shortest Path First (OSPF) is a link state
Router Networks
protocol.
R1 Network 1
Each router reports to its neighbors the Network 2
characteristics of its active connections to local R2 Network 3
networks
networks. R3 Network 4
…
Updates are flooded, unchanged, to all routers
within an administratively defined area, and the
routers store the information.
Each router uses this first-hand information to
calculate its shortest path to each address Link-state algorithm runs on
database contents, producing
range.
IP route table entries.
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.
RIP’s 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 RIP’s rules and how to

p RIP routes as theyy appear
interpret pp in the route table.
Rev. 10.41 3-5

RIP Advertisements: 1
The Routing Information Protocol (RIP) uses a distance-
vector algorithm to determine the best path to each
destination. VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24 RouterA
Routers periodically advertise their route table entries VLAN 100: 10.1.100.1/24
g , or p
to RIP neighbors, peers. Loop 0: 10.1.0.25/32
10.1.100.1/24
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.
10.1.100.2/24
VLAN 30: 10.1.30.1/24 RouterB

VLAN 40: 10.1.40.1/24
VLAN 100: 10.1.100.2/24
Loop 0: 10.1.0.26/32
RIP Advertisements: 2
VLAN 10: 10.1.10.1/24

Ethernet header: VLAN 20: 10.1.20.1/24 RouterA
Dest: 01005e-000009 Source: <RouterA MAC> VLAN 100: 10.1.100.1/24
Loop 0: 10.1.0.25/32
IP datagram
d t h
header:
d
Protocol: UDP RIP v2 updates are 10.1.100.1/24
R
Source: 10.1.100.1 Dest: 224.0.0.9 sent to a reserved I
multicast address P
UDP header:
Source: 520 (RIP) Dest: 520 (RIP) U
This router is configured to use split D
Routing Information Protocol: horizon loop prevention. It does not P
Command: Response (2) Version: RIPv2 (2) include 10.1.100.0/24, which is the
Network: 10.1.0.25 Mask: 255.255.255.255 Metric: 1 address range associated with the I
P
network that carries this RIP update.
Network: 10.1.10.0 Mask: 255.255.255.0 Metric: 1
Network: 10.1.20.0 Mask: 255.255.255.0 Metric: 1 M
A
C
Ethernet trailer: <Checksum value> 10.1.100.2/24
VLAN 30: 10.1.30.1/24 RouterB

VLAN 40: 10.1.40.1/24
VLAN 100: 10.1.100.2/24
Loop 0: 10.1.0.26/32
Rev. 10.41 3-6

Updating the Route Table
Before RouterB receives the RIP advertisement from RouterA,

its route table contains only directly connected networks.
VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24 RouterA
When it receives RouterA’s RIP advertisement, RouterB VLAN 100: 10.1.100.1/24
integrates the address ranges into its route table, and Loop 0: 10.1.0.25/32
increments
i the advertised
t th d ti d costs.
t
10.1.100.1/24
IP Route Table: RouterB
Destination Gateway VLAN Type Metric

10.1.0.25/32 10.1.100.1 100 rip 2
10.1.0.26/32 lo0 connected 1 These networks
10.1.10.0/24 10.0.100.1 100 rip 2 were advertised
10.1.20.0/24 10.0.100.1 100 rip 2 with a cost of 1.
10.1.30.0/24 VLAN30 30 connected 1
10.1.40.0/24 VLAN40 40 connected 1
10 1 100 0/24
10.1.100.0/24 VLAN100
100 100 connected
d 1
10.1.100.2/24
VLAN 30: 10.1.30.1/24 RouterB

VLAN 40: 10.1.40.1/24
VLAN 100: 10.1.100.2/24
Loop 0: 10.1.0.26/32
Generating RIP Advertisements:1

The router generates a unique advertisement to send over each of its RIP
interfaces, based on the content of its route table.
The advertisement RouterB sends to RouterC includes its own connected RouterA
networks and those it learned from RouterA.
10.1.100.1/24
IP Route Table: RouterB

10.1.0.25/32 10.1.100.1 100 rip 2
10.1.0.26/32 lo0 connected 1
10.1.10.0/24 10.0.100.1 100 rip 2
10.1.20.0/24 10.0.100.1 100 rip 2
10.1.30.0/24 VLAN30 30 connected 1
10.1.40.0/24 VLAN40 40 connected 1
0. . 00.0/
10.1.100.0/24 VLAN100
00 100
00 co
connected
ected 1
10.1.100.2/24
Connected networks:
VLAN 50: 10.1.50.1/24
VLAN 60: 10.1.60.1/24 RouterC RouterB
.1 .2
VLAN 101: 10.1.101.1/24 10.1.101.0/24
Loop 0: 10.1.0.27/32
Rev. 10.41 3-7

Generating RIP Advertisements: 2

The router generates a unique advertisement to send over each of its RIP
interfaces, based on the content of its route table.
The advertisement RouterB sends to RouterC includes its own connected RouterA
networks and those it learned from RouterA.: RouterB - VLAN 101 interface -10.1.101.2
RIP advertisement
Ethernet header:
Dest: 01005e-000009 Source: <RouterB MAC>
10.1.100.1/24
IP datagram header:
Protocol: UDP IP Route Table: RouterB
Source: 10.1.101.2 Dest: 224.0.0.9
Destination
UDP header: Gateway VLAN Type Metric
10.1.0.25/32 10.1.100.1 100 rip 2
Source: 520 (RIP) Dest: 520 (RIP)
10.1.0.26/32 lo0 connected 1
Routing
10.1.10.0/24 Information Protocol:
10.0.100.1 100 rip 2
Command: Response
10.1.20.0/24 (2) Version:
10.0.100.1 100RIPv2 rip
(2) 2
Network: 10.1.0.25
10.1.30.0/24 VLAN30Mask: 255.255.255.255
30 Metric: 21
connected
Network: 10.1.0.26
10.1.40.0/24 VLAN40Mask: 255.255.255.255
40 Metric: 11
connected
Network:
/
10.1.100.0/24 10.1.10.0 Mask: 255.255.255.0
VLAN100 100 Metric: 2 1
connected
Network: 10.1.40.0 Mask: 255.255.255.0 Metric: 1 10.1.100.2/24
Connected networks: Network: 10.1.100.0 Mask: 255.255.255.0 Metric: 1
VLAN 50: 10.1.50.1/24
.1 .2
VLAN 101: 10.1.101.1/24 10.1.101.0/24
Loop 0: 10.1.0.27/32
Adding RIP Routes to the Table

RouterC integrates the advertised address ranges into its route table,
incrementing the costs.
RouterA
IP Route Table: RouterC
10.1.0.25/32 10.1.101.2 100 rip 3 10.1.100.1/24
10.1.0.26/32 l0.1.101.2 100 rip 2
10.1.0.27/32 lo0 connected 1
10.1.10.0/24 10.1.101.2 100 rip 3
10.1.20.0/24 10.0.101.2 100 rip 3
10.1.30.0/24 10.0.101.2 100 rip 2
10.1.40.0/24 10.0.101.2 100 rip 2
10.1.50.0/24 VLAN50 50 connected 1
10.1.60.0/24 VLAN60 60 connected 1
10.1.100.0/24 10.0.101.2 100 rip 2
10.1.101.0/24 VLAN101 101 connected 1
10.1.100.2/24
Connected networks:
VLAN 50: 10.1.50.1/24
.1 .2
VLAN 101: 10.1.101.1/24 10.1.101.0/24
Loop 0: 10.1.0.27/32
Rev. 10.41 3-8

Adding a Redundant Routed Link

When another link is added, RouterC receives RIP updates from
RouterA that advertise a shorter path to some destinations.
The router increments the advertised cost of each network within the Connected networks:
RouterA VLAN 10: 10.1.10.1/24
update, and compares this value with the cost associated with the VLAN 20: 10.1.20.1/24
network in the route table. VLAN 100: 10.1.100.1/24
VLAN 102
102: 10
10.1.102.2/24
1 102 2/24
.2 .1 Loop 0: 10.1.0.25/32
10.1.0.25/32 10.1.101.2 100 rip 3
10.1.0.26/32 l0.1.101.2 100 rip 2
10.1.0.27/32 lo0 connected 1
10.1.10.0/24 10.1.101.2 100 rip 3 10.1.102.0/24
10.1.20.0/24 10.0.101.2 100 rip 3
10.1.30.0/24 10.0.101.2 100 rip 2
10.1.40.0/24 10.0.101.2 100 rip 2 10.1.100.0/24
10.1.50.0/24 VLAN50 50 connected 1
10.1.60.0/24 VLAN60 60 connected 1
10.1.100.0/24 10.0.101.2 100 rip 2
10.1.101.0/24 VLAN101 101 connected 1
.1 .2
Connected networks: RouterC RouterB Connected networks:
VLAN 50: 10.1.50.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.60.1/24 10.1.101.0/24 VLAN 40: 10.1.40.1/24
.1 .2
VLAN 101: 10.1.101.1/24 VLAN 100: 10.1.100.2/24
VLAN 102: 10.1.102.1/24 VLAN 101: 10.1.101.2/24
Loop 0: 10.1.0.27/32 Loop 0: 10.1.0.26/32
Replacing Route Table Entries: 1

The router replaces entries whose calculated cost is lower than the
cost for that network in the route table.
When replacing route table entries, the router updates the value in the Connected networks:
RouterA
“Gateway” field to match the “Source address” field in the IP VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24
datagram header.
VLAN 100: 10.1.100.1/24
VLAN 102
102: 10
10.1.102.2/24
1 102 2/24
.2 .1 Loop 0: 10.1.0.25/32
10.1.0.25/32 10.1.101.2 100 rip 3
10.1.0.26/32 l0.1.101.2 100 rip 2
10.1.0.27/32 lo0 connected 1
10.1.10.0/24 10.1.101.2 100 rip 3 10.1.102.0/24
10.1.20.0/24 10.0.101.2 100 rip 3
10.1.30.0/24 10.0.101.2 100 rip 2
10.1.40.0/24 10.0.101.2 100 rip 2 10.1.100.0/24
10.1.50.0/24 VLAN50 50 connected 1
10.1.60.0/24 VLAN60 60 connected 1
10.1.100.0/24 10.0.101.2 100 rip 2
10.1.101.0/24 VLAN101 101 connected 1
.1 .2
VLAN 50: 10.1.50.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.60.1/24 10.1.101.0/24 VLAN 40: 10.1.40.1/24
.1 .2
VLAN 101: 10.1.101.1/24 VLAN 100: 10.1.100.2/24
VLAN 102: 10.1.102.1/24 VLAN 101: 10.1.101.2/24
Loop 0: 10.1.0.27/32 Loop 0: 10.1.0.26/32
Rev. 10.41 3-9

Replacing Route Table Entries: 2

The router replaces entries whose calculated cost is lower than the
cost for that network in the route table.
RIP advertisement : RouterA int 10.1.102.2
When replacing route table entries, the router updates the value in the Connected networks:
… RouterA
“Gateway” field to match the “Source address” field in the IP IP datagram header:
VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24
datagram header. Protocol: UDP
VLAN 100: 10.1.100.1/24
Source: 10.1.102.2 Dest: 224.0.0.9
UDP header: VLAN 102102: 10
10.1.102.2/24
1 102 2/24
Dest: 520Loop
.2 (RIP) .1
Source: 520 (RIP) 0: 10.1.0.25/32
Destination Gateway VLAN Type Metric Routing Information Protocol:
10.1.0.25/32 10.1.102.2 102 rip 2 Network: 10.1.0.25 Mask: 255.255.255.255 Metric: 1
10.1.0.26/32 l0.1.101.2 100 rip 2 Network: 10.1.0.26 Mask: 255.255.255.255 Metric: 2
10.1.0.27/32 lo0 connected 1 Network: 10.1.0.27 Mask: 255.255.255.255 Metric: 3
10.1.100.0/24
10.1.50.0/24 VLAN50 50 connected 1 Network: 10.1.50.0 Mask: 255.255.255.0 Metric: 3
.1 .2
VLAN 50: 10.1.50.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.60.1/24 10.1.101.0/24 VLAN 40: 10.1.40.1/24
.1 .2
VLAN 101: 10.1.101.1/24 VLAN 100: 10.1.100.2/24
VLAN 102: 10.1.102.1/24 VLAN 101: 10.1.101.2/24
Loop 0: 10.1.0.27/32 Loop 0: 10.1.0.26/32
Split Horizon Loop Protection: 1

Following Split Horizon rules, RouterC’s subsequent RIP
advertisements to RouterA will omit the routes it has learned
through its connection to RouterA.
Connected networks:
RouterA 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
.2 .1 Loop 0: 10.1.0.25/32
10.1.0.25/32 10.1.102.2 102 rip 2
10.1.0.26/32 l0.1.101.2 100 rip 2
10.1.0.27/32 lo0 connected 1
10.1.10.0/24 10.1.102.2 102 rip 2 10.1.102.0/24
10.1.20.0/24 10.0.102.2 100 rip 2
10.1.30.0/24 10.0.101.2 100 rip 2
10.1.40.0/24 10.0.101.2 100 rip 2 10.1.100.0/24
10.1.50.0/24 VLAN50 50 connected 1
10.1.60.0/24 VLAN60 60 connected 1
10.1.100.0/24 10.0.101.2 100 rip 2
10.1.101.0/24 VLAN101 101 connected 1
.2
.1
VLAN 50: 10.1.50.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.60.1/24 10.1.101.0/24
.1 .2 VLAN 40: 10.1.40.1/24
VLAN 101: 10.1.101.1/24 VLAN 100: 10.1.100.2/24
VLAN 102: 10.1.102.1/24 VLAN 101: 10.1.101.2/24
Loop 0: 10.1.0.27/32 Loop 0: 10.1.0.26/32
Rev. 10.41 3 - 10
Split Horizon Loop Protection: 2

Following Split Horizon rules, RouterC’s subsequent RIP
advertisements to RouterA will omit the routes it has learned
through its connection to RouterA.
Connected networks:
RouterA
Split Horizon can decrease convergence time in a meshed VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24
topology.
VLAN 100: 10.1.100.1/24
VLAN 102
102: 10
10.1.102.2/24
1 102 2/24
.2 .1 Loop 0: 10.1.0.25/32
10.1.0.25/32 10.1.102.2 102 rip 2
10.1.0.26/32 l0.1.101.2 100 rip 2
10.1.0.27/32 lo0 connected 1
10.1.10.0/24 10.1.102.2 102 rip 2 10.1.102.0/24
10.1.20.0/24 10.0.102.2 100 rip 2
10.1.30.0/24 10.0.101.2 100 rip 2
10.1.40.0/24 10.0.101.2 100 rip 2 10.1.100.0/24
10.1.50.0/24 VLAN50 50 connected 1
10.1.60.0/24 VLAN60 60 connected 1
10.1.100.0/24 10.0.101.2 100 rip 2
10.1.101.0/24 VLAN101 101 connected 1 RIP advertisement : RouterC int 10.1.102.1

.2
Connected networks: Network: 10.1.40.0 Mask: 255.255.255.0
RouterB Metric:
Connected 2
networks:
RouterC .1
VLAN 50: 10.1.50.1/24 Network: 10.1.50.0 Mask: 255.255.255.0
VLAN Metric: 1
30: 10.1.30.1/24
VLAN 60: 10.1.60.1/24 10.1.101.0/24
.1 .2 VLAN 40: 10.1.40.1/24
VLAN 101: 10.1.101.1/24 Network: 10.1.100.0 Mask: 255.255.255.0 Metric:
VLAN 100: 2
10.1.100.2/24
VLAN 102: 10.1.102.1/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.27/32 Loop 0: 10.1.0.26/32
Poisoned Reverse Loop Protection: 1

Poisoned reverse is a variation on split horizon. Instead of omitting routes it learned from a neighbor,
the RIP updates advertise these routes are advertised with a cost of 16, which means “unavailable.”
Connected networks:
RouterA 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
.2 .1 Loop 0: 10.1.0.25/32

10.1.0.25/32 10.1.102.2 102 rip 2 10.1.102.0/24
10.1.0.26/32 l0.1.101.2 100 rip 2
10.1.0.27/32 lo0 connected 1
10.1.10.0/24 10.1.102.2 102 rip 2 10.1.100.0/24
10.1.20.0/24 10.0.102.2 100 rip 2
10.1.30.0/24 10.0.101.2 100 rip 2
10.1.40.0/24 10.0.101.2 100 rip 2
10.1.50.0/24 VLAN50 50 connected 1
10.1.60.0/24 VLAN60 60 connected 1
10.1.100.0/24 10.0.101.2 100 rip 2
10.1.101.0/24 VLAN101 101 connected 1
.2
.1
VLAN 50: 10.1.50.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.60.1/24 10.1.101.0/24
.1 .2 VLAN 40: 10.1.40.1/24
VLAN 101: 10.1.101.1/24 VLAN 100: 10.1.100.2/24
VLAN 102: 10.1.102.1/24 VLAN 101: 10.1.101.2/24
Loop 0: 10.1.0.27/32 Loop 0: 10.1.0.26/32
Rev. 10.41 3 - 11
Poisoned Reverse Loop Protection: 2

Poisoned reverse is a variation on split horizon. Instead of omitting routes it learned from a neighbor,
the RIP updates advertise these routes are advertised with a cost of 16, which means “unavailable.”
RouterC poisons the routes it has learned from RouterA only within the Connected networks:
advertisements it sends to RouterA. The updates RouterC sends to RouterA VLAN 10: 10.1.10.1/24
RouterB will advertise these routes with actual costs from its route table. VLAN 20: 10.1.20.1/24
VLAN 100: 10.1.100.1/24
IIn certain
t i meshed
h d ttopologies,
l i poisoned
i d reverse can iimprove VLAN 102
102: 10
10.1.102.2/24
1 102 2/24
convergence speed when compared with split horizon. .2 .1 Loop 0: 10.1.0.25/32

RIP advertisement : RouterC int 10.1.102.1
10.1.102.0/24
10.1.0.26/32 l0.1.101.2 100 rip 2 Network: 10.1.0.26 Mask: 255.255.255.255 Metric: 2
10.1.0.27/32 lo0 connected 1 Network: 10.1.0.27 Mask: 255.255.255.255 Metric: 1
10.1.10.0/24 10.1.102.2 102 rip 2 Network: 10.1.10.0 Mask:10.1.100.0/24
255.255.255.0 Metric: 16
10.1.20.0/24 10.0.102.2 100 rip 2
10.1.30.0/24 10.0.101.2 100 rip 2
10.1.40.0/24 10.0.101.2 100 rip 2
10.1.50.0/24 VLAN50 50 connected 1 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.101.0 Mask: 255.255.255.0
.2 Metric: 1
.1
VLAN 50: 10.1.50.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.60.1/24 10.1.101.0/24
.1 .2 VLAN 40: 10.1.40.1/24
VLAN 101: 10.1.101.1/24 VLAN 100: 10.1.100.2/24
VLAN 102: 10.1.102.1/24 VLAN 101: 10.1.101.2/24
Loop 0: 10.1.0.27/32 Loop 0: 10.1.0.26/32
RIP Automatic Summarization: 1

Loop 0: 172.16.0.26/32
Routers A, B, and C are connected to another set of routers VLAN 30: 172.16.30.1/24
whose network addresses are within a different classful VLAN 40: 172.16.40.1/24 Loop 0: 172.16.0.27/32
network." VLAN 101: 172.16.101.1/24 VLAN 50: 172.16.50.1/24
VLAN 102: 172.16.102.2/24 VLAN 102: 172.16.102.1/24
Router D has interfaces in both classful networks, so its route
RouterD RouterA
table shows individual subnets within each of the networks.
172.16.102.0/24
Router D summarizes all of the address space within
172.16.0.0/16 in the RIP updates it sends over VLAN
100. It advertises individual networks within the
10.0.0.0/8 range because the address associated with 172.16.101.0/24
the VLAN 100 is within that range.
Loop 0: 172.16.0.25/32
VLAN 10: 172.16.10.1/24
VLAN 20: 172.16.20.1/24 RouterD RouterA
VLAN 100: 10.0.100.1/24
VLAN 101: 172.16.101.2/24
RIP advertisement : RouterC int 10.1.102.1 .1
Network: 10.0.100.0 Mask: 255.255.255.0 Metric: 16 10.0.100.0/24

RouterC RouterB
…
Rev. 10.41 3 - 12
RIP Automatic Summarization: 2

Loop 0: 172.16.0.26/32
Routers A, B, and C are connected to another set of routers VLAN 30: 172.16.30.1/24
whose network addresses are within a different classful VLAN 40: 172.16.40.1/24 Loop 0: 172.16.0.27/32
network." VLAN 101: 172.16.101.1/24 VLAN 50: 172.16.50.1/24
VLAN 102: 172.16.102.2/24 VLAN 102: 172.16.102.1/24
Router D has interfaces in both classful networks, so its route
RouterD RouterA
table shows individual subnets within each of the networks.
172.16.102.0/24
Router D summarizes all of the address space within
172.16.0.0/16 in the RIP updates it sends over VLAN
100. It advertises individual networks within the
10.0.0.0/8 range because the address associated with 172.16.101.0/24
the VLAN 100 is within that range.
Loop 0: 172.16.0.25/32
VLAN 10: 172.16.10.1/24 .2
VLAN 20: 172.16.20.1/24 RouterD RouterA
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 RIP advertisement : RouterC int 172.16.101.2
172 16 101 2
a single advertisement to summarize the address space 10.0.100.0/24
within 10.0.0.0/8. It advertises individual networks …
within the 172.16.0.0/16 range because the address Network: 172.16.0.25 Mask: 255.255.255.255 Metric: 1
associated with the VLAN 101 is within that range. Network: 172.16.0.27 Mask: 255.255.255.255 Metric: 16
Network: 172.16.10.0 Mask: 255.255.255.0 Metric:
RouterC RouterB 1
…
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
Dynamic Route Exchange

This diagram illustrates a hierarchical topology that requires all traffic between locations to transit the core.
Routers at locations A, B, and C
advertise each of their networks to
neighbor routers in the intranet core.
Routers in the intranet core advertise to
each location the networks in all other Intranet core range:
locations. 10.0.0.0/16 Location C range:
10.3.0.0/16
Without further RIP configuration, each
router will need to support up to 1,024
route table entries.
RIP updates
Location A range: Location B range:

10.1.0.0/16 10.2.0.0/16
The Effect of Large IP Route Tables
Dynamic routing updates have the benefit of providing routers with the information they need to find the
best path to a given destination. However, the unrestricted flow of a large number of dynamic routing
updates can impact performance in two important ways:
1 A large number of RIP update packets sent at frequent

1.
0101 0 010 010 101 010 0101 0 010 010 101 010
0110 1 110 000 111 010
0101 0 010 010 101 110
intervals can impact network performance.

0001 1 010 010 101 010
0111 0 000 110 101 000
1101 0 010 000 101 010
0001 1 010 110 101 010
0111 0 010 011 101 010
0011 1 010 110 101 010
Each RIP update interval (default: 30 seconds) may

1101 0 010 000 101 010
require several update packets to contain all of the

networks to be advertised.
2. A large number of route table entries can impact router
performance.
Modern router architecture typically relies on packet
cache and other techniquesq to minimize occasions when
packets must be submitted to the entire route table for
lookup. However, when the router performs a lookup on
the first packet in a flow, a smaller route table is more
desirable.
Rev. 10.41 3 - 14
Technet24.ir
Using a Default Static Route

There is another important reason to restrict dynamic routing updates between each location and the
intranet core in this scenario:
This router interface
Locations A, B, and C use a single point- provides the next hop for
to-point link to reach all remote the static default route.
destinations This fact makes it
destinations.
Intranet core range: Networks 10.3.0.0/24
unnecessary to maintain details
10.0.0.0/16 – 10.3.0.255.0/24
regarding the networks at other
locations.
Define static
All 4 billion addresses in the IP address default route here
space may be summarized as the default
route: 0.0.0.0/0.

10.1.0.0/16 10.2.0.0/16
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. Intranet core range:
10 0 0 0/16
10.0.0.0/16 Location C range:
The next hop for each range will be a RC 10.3.0.0/16
neighboring router interface at the
remote location.
Network summarization requires that all
networks within the summarized range
must be reachable through the next hop RA
router interface. RB
10 1 0 0/16
10.1.0.0/16 10 2 0 0/16
10.2.0.0/16
Rev. 10.41 3 - 15
Redundant Static Routes
Many routers and routing switches support configuration of multiple static routes that specify the same
destination.
If static routes are defined with different
costs, the router will send all traffic to the
next hop defined in the lowest
lowest-cost
cost route
route.
Higher-cost routes will be used only after Intranet core range:
10.0.0.0/16 RC2 Location C range:
failure of lower cost routes.
10.3.0.0/16
RC1
A router’s use of equal-cost static routes
will depend on whether it supports a
feature typically referred to as “ECMP,”
or Equal-Cost MultiPath.
RB2
HP Networking E-series routing switches RA1 RA2
support load sharing for equal-cost static RB1
routes. 10.2.0.0/16
10.1.0.0/16
Most Specific Route Table Match

Route table entries specify a range of addresses that are defined using a starting address and mask.
Some entries represent a single network, a VLAN or broadcast domain. Other entries may specify an
address range that corresponds with a larger range of addresses.
When a packet is submitted for lookup, its destination address is compared with the contents of the route
table. It mayy match with multiple
p entries.
Th
Three entries in this
h route table
bl
When a packet matches with multiple match with the destination 10.1.1.15.
route table entries, it is forwarded using
the gateway associated with the entry IP Route Table
that has the longest mask. This is also
Destination Gateway VLAN Type Metric Distance
referred to as the “most specific match.” 0.0.0.0 10.0.100.100 100 static 1 1
10.0.100.0/24 VLAN100 100 connected 1 0
All destinations match with the 10.1.0.0/16 10.0.102.1 102 static 1 1
default route (0.0.0.0/0). 10.1.1.0/24
10.1.2.0/24
VLAN1
VLAN2
1
2
connected
connected
1
1
0
0
The router discards packets that do
10.1.10.0/24 10.1.64.2 64 rip 3 120
10.1.20.0/24 10.1.64.2 64 rip 3 120
not match any entries. 10.1.30.0/24 VLAN30 30 connected 1 0
10.1.40.0/24 VLAN40 40 connected 1 0
10.1.64.0/24 VLAN64 64 connected 1 0
10.2.0.0/16 10.0.100.2 100 static 1 1
This is the most specific match for

the destination 10.1.1.15.
Rev. 10.41 3 - 16
Technet24.ir
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
Default administrative distances for
Destination Gateway VLAN Type Metric Distance this router:
0.0.0.0 10.0.100.100 100 static 1 1
10.0.100.0/24
10.1.0.0/16
VLAN100
10.0.102.1
100
102
connected
static
1
1
0
1
• Directly connected networks: 0
10.1.1.0/24
10.1.2.0/24
VLAN1
VLAN2
1
2
connected
connected
1
1
0
0
• Static routes: 1
10.1.10.0/24
10.1.20.0/24
10.1.64.2
10.1.64.2
64
64
rip
rip
3
3
120
120
• RIP-learned routes: 120
• OSPF-learned
OSPF learned routes: 110
10.1.30.0/24 VLAN30 30 connected 1 0
10.1.40.0/24 VLAN40 40 connected 1 0
10.1.64.0/24 VLAN64 64 connected 1 0
10.2.0.0/16 10.0.100.2 100 static 1 1
Static Route Redistribution into RIP

Router A1: IP Route Table
In the example, the static route is defined
on Router A1, which is the router whose Destination
0.0.0.0
Gateway
10.0.100.100
VLAN
100
Type
static
Metric
1
Distance
1
neighbor leads to the remote address 10.1.1.0/24 VLAN1 1 connected 1 0
range 10.0.0.0/16. 10.1.10.0/24 10.1.64.2 64 rip 3 120
10.1.20.0/24 10.1.64.2 64 rip 3 120
Router A1 will advertise static routes 10.1.30.0/24 VLAN30 30 connected 1 0
within
h its RIP update
d messages iff RIP
10 1 40 0/24
10.1.40.0/24 VLAN40 40 connected 1 0
...
redistribution is enabled. 10.1.64.0/24 VLAN64 64 connected 1 0
Address range:
10.0.0.0/16
Address range:
Static route was defined here: A1 10.1.0.0/16
ip route 0.0.0.0/0 10.0.100.100 A3
Router A2: IP Route Table

A5
Destination Gateway VLAN Type Metric Distance A2
0.0.0.0 10.1.64.1 64 rip 2 120
10.1.1.0/24 VLAN1 1 connected 1 0 A4
10.1.10.0/24 VLAN10 64 rip 3 120
10.1.20.0/24 VLAN20 64 rip 3 120
10.1.30.0/24 10.1.64.1 64 rip 2 120
10.1.40.0/24 10.1.64.1 64 connected 1 0
...
10.1.64.0/24 VLAN64 64 connected 1 0
Rev. 10.41 3 - 17
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
Technet24.ir
HP Switching and Routing Technologies Open Shortest Path First (OSPF)
Module 4: Open Shortest Path First (OSPF)

Objectives
An intranet with redundant routed links will make the best use of the resilient design when it uses
the OSPF routing protocol, which can quickly respond to changes in link states.
• Describe OSPF characteristics that make it suitable to resilient
resilient, large-scale intranets
intranets.
• Describe how routing information propagates throughout an OSPF domain.
• List OSPF router roles and the significance each has to sharing routing information.
• Explain the functions of the OSPF message types.
• Describe the OSPF area types and their proper uses.
• Describe how remote address space is summarized within an OSPF domain.
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 iis able
bl tto consider
id lilinkk 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 Network C
Cost 100
connected networks.
An OSPF router floods advertisements from its Network B
Network
N t kA
Cost 10
neighbors to all other neighbors intact, without Cost 100
R1
changing the contents of the advertisements.
Rev. 10.41 4-1

OSPF Hierarchy: Routers and Networks
OSPF routers:
• Are uniquely identified by a 32-bit OSPF Router 10.0.0.32
dotted decimal value. VLAN 100: 10.1.100.1
p 0: 10.0.0.32
Loop
• Establish a formal relationship, known
10.0.0.32
as adjacency, with neighbors
All five routers
OSPF networks are identified by a starting are neighbors
address and mask. on this network.
10.0.100.0/24
OSPF Router 10.1.0.32 10.1.0.32 10.2.0.32 OSPF Router 10.2.0.32

VLAN 100: 10.0.100.2 VLAN 100: 10.0.100.4
Loop 0: 10.1.0.32/32 Loop 0: 10.2.0.32/32
OSPF Router 10.1.0.33 10.1.0.33 10.2.0.33 OSPF Router 10.2.0.33

VLAN 100: 10.0.100.3 VLAN 100: 10.0.100.5
Loop 0: 10.1.0.33/32 Loop 0: 10.2.0.33/32
OSPF Network Types and Adjacency
Adjacency is a two-way relationship

between a pair of OSPF routers that
enables them to share routing information.
For the purposes of forming adjacency,
an OSPF network is classified by the
number of neighbors it will support.
• A point-to-point network can
support at most two router
interfaces. The routers will form
an adjacency.
• A multi-access network, such as Ethernet, can
support more than two router interfaces. The
q
number of connections required to create a full
mesh of point-to-point adjacencies increases
significantly as neighbors are added.
A full mesh would
require 10 point-to-
point adjacencies
N * (N – 1)/2
Rev. 10.41 4-2

Technet24.ir
Designated Router and Backup Designated Router
OSPF routers with interfaces on multi-

access networks may not always form a full
adjacency with all neighbors.
A Designated Router (DR) is elected for each

multi-access network. The DR forms an
adjacency with all neighbors on the network.
An elected Backup Designated Router (BDR)

also becomes adjacent with all neighbors on
the network.
Non-DRs are adjacent to the DR and BDR,
but do not become adjacent to each other.
DR BDR
OSPF Hierarchy: Areas

OSPF Autonomous System (AS)
The next level of OSPF hierarchy is
the area. Areas are identified by a Area 0.0.0.0
dotted decimal number.
OSPF area boundaries define the Area

ea 1.0.0.0
.0.0.0 Area
ea 2.0.0.0
.0.0.0
scope of certain types of link state
advertisements. IP address space
may be summarized at area
boundaries.
Each network can belong to only

one area. The router interfaces
connected to a given network can
form adjacencies only if they agree
on its Area ID
ID.
The highest level in the hierarchy is

the Autonomous System (AS), which
is a collection of OSPF areas under
common administration.
Rev. 10.41 4-3

Area Border Routers (ABR): 1

OSPF Autonomous System (AS)
OSPF areas are interconnected by
area border routers (ABR). Area Area 0.0.0.0
border routers are configured with
at least one interface in the
Autonomous System “backbone”
backbone Area 1.0.0.0 Area
ea 2.0.0.0
.0.0.0
area, which interconnects all other
areas and uses the reserved ID
0.0.0.0.
Area Border Routers (ABR): 2
ABRs maintain adjacencies

with neighbors in two
OSPF Router 10.1.0.32 different areas. OSPF Router 10.1.0.33
Area 0.0.0.0 Networks: Area 0.0.0.0 Networks:
VLAN 100: 10.0.100.2/24/ 10.0.100.0/24
/ 10.0.100.0/24
/ VLAN 100: 10.0.100.3/24/
Loop 0: 10.1.0.32/32 Loop 0: 10.1.0.33/32
VLAN 64: 10.1.64.1/24 VLAN 64: 10.1.64.2/24
10.1.64.0/24
VLAN 65: 10.1.65.1/24 VLAN 66: 10.1.66.1/24
VLAN 67: 10.1.67.1/24 VLAN 68: 10.1.68.1/24
10.1.67.0/24
10.1.65.0/24 10.1.66.0/24
10.1.68.0/24
OSPF Router 10.1.0.34 OSPF Router 10.1.0.35
p 0: 10.1.0.34/32
Loop / oop 0: 10.1.0.35/32
Loop 0. .0.35/3
VLAN 65: 10.1.65.2/24 VLAN 66: 10.1.66.2/24
VLAN 68: 10.1.68.2/24 VLAN 67: 10.1.67.2/24
VLAN 10: 10.1.10.1/24 VLAN 30: 10.1.30.1/24
VLAN 20: 10.1.20.1/24 10.1.10.0/24 All interfaces of 10.1.30.0/24 VLAN 40: 10.1.40.1/24
each non-ABR are
10.1.20.0/24 located within the 10.1.40.0/24
same area.
Rev. 10.41 4-4

Technet24.ir
OSPF Router Startup

When OSPF is activated on a router, it generates a link state
advertisement (Router LSA) that describes the characteristics OSPF Area 1.0.0.0 Networks:
RouterA
of its connected networks. VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
This advertisement, which is indexed by the unique Router VLAN 64: 10.1.64.1/24
Loop 0: 10.1.0.25/32
ID,, is stored in a database and transmitted to the router’s
neighbors after they have begun to form an adjacency.
Most routers enable static configuration of a Router ID. In the
absence of static configuration, many routers will choose an
address associated with the router’s loopback interface.
Router ID: 10.1.0.25 Area 1.0.0.0 Link State Database

Link State Advertisement Type: Router LSA (1)
Link State ID: 10.1.0.25
Advertisingg Router: 10.1.0.25
Number of Links: 4
Type: Stub ID: 10.1.0.25 Data: 255.255.255.255 Metric: 1
ID: 10.1.0.26
RouterB
The networks are considered “Stub” type because the router has no
adjacent neighbors on these networks.
Exchanging Hello Messages: 1

Link state advertisements can flow only over adjacencies. This
makes adjacency establishment an important initial goal for
each OSPF interface. OSPF Area 1.0.0.0 Networks:
RouterA
VLAN 10: 10.1.10.1/24
The Hello message is the first step in establishing VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
adjacency. In the example, RouterA has four connected VLAN 64: 10.1.64.1/24
Loop 0: 10.1.0.25/32
g over all
networks. The router will send Hello messages
active interfaces. O
S
Ethernet header: P
F
Dest: 01005e-000005 Source: <RouterA MAC>
I
OSPF Hello P
IP datagram header: messages are sent
M
Protocol: 89 (OSPF) to a reserved A
Source: 10.1.64.1 Dest: 224.0.0.5 multicast address 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: ID: 10.1.0.26
Network Mask: 255.255.255.0
Hello interval: 10 seconds This router has no
Router Priority: 1 neighbors on this
Router Dead Interval: 40 seconds network. It assumes the RouterB
Designated Router: 10.1.64.1 role of Designated Router.
Backup Designated Router: 0.0.0.0
Rev. 10.41 4-5

Exchanging Hello Messages: 2

makes adjacency establishment an important initial goal for
each OSPF interface. OSPF Area 1.0.0.0 Networks:
RouterA
VLAN 10: 10.1.10.1/24
The Hello message is the first step in establishing VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
adjacency. In the example, RouterA has four connected VLAN 64: 10.1.64.1/24
Loop 0: 10.1.0.25/32
g over all
networks. The router will send Hello messages
S
RouterA continues sending periodic Hello packets indefinitely, P
regardless of whether any neighboring routers reply with

F
I
Hello packets. P
M
When OSPF is enabled on RouterB, it begins sending Hello A
messages as well. C
ID: 10.1.0.26
RouterB
Synchronizing Link State Databases

makes adjacency establishment an important initial goal for OSPF Area 1.0.0.0 Networks:
each OSPF interface. RouterA
VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
The Hello message is the first step in establishing VLAN 64: 10.1.64.1/24
adjacency. In the example, RouterA has four connected Loop 0: 10.1.0.25/32
networks The ro
networks. router
ter will send Hello messages over
o er all
S
P
RouterA continues sending periodic Hello packets indefinitely, F
regardless of whether any neighboring routers reply with I
Hello packets. P
M
When OSPF is enabled on RouterB, it begins sending Hello A
C
messages as well.
ID: 10.1.0.26
RouterB
Rev. 10.41 4-6

Technet24.ir
Synchronizing Link State Databases: 1

A goal of adjacency is the initial synchronization of the
contents of the two neighbors’ link state databases. OSPF Area 1.0.0.0 Networks:
RouterA
In the next phase of adjacency formation, each router VLAN 10: 10.1.10.1/24
VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
describes the contents of its link state database by VLAN 64: 10.1.64.1/24
sending the headers of its stored link state advertisements Loop 0: 10.1.0.25/32
(LSA) within Database Description packets.
packets
Database
RouterA sends its LSA headers, and RouterB Description
compares the neighbor’s headers with those in its Packet
own database.
OSPF Area 1.0.0.0 Networks: ID: 10.1.0.26

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 RouterB

RouterA
VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
describes the contents of its link state database by
VLAN 64: 10.1.64.1/24
packets
Database
RouterA sends its LSA headers, and RouterB compares the Description
neighbor’s headers with those in its own database. Packet
Ethernet header:
Dest: <RouterB MAC> Source: <RouterA MAC>
IP datagram header: Database Description packets

Protocol: 89 (OSPF) are sent to the neighbor’s
Source: 10.1.64.1 Dest: 10.1.64.2 unicast IP address.
OSPF Header:
OSPF Version: 2
Message Type: DB Descr. (2)
Area: 1.0.0.0 OSPF Area 1.0.0.0 Networks: ID: 10.1.0.26
Database Description Header: These items identify this VLAN 30: 10.1.30.1/24
LSA Type: Router LSA (1) VLAN 40: 10.1.40.1/24
message as the first instance
Link State ID: 10.1.0.25 VLAN 64: 10.1.64.2/24
Advertising Router: 10.1.0.25 of the Router LSA advertised RouterB
Loop 0: 10.1.0.26/32
LS Sequence Number: 80000000 by Router ID 10.1.0.25.
…
Rev. 10.41 4-7


RouterA
VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
describes the contents of its link state database by VLAN 64: 10.1.64.1/24
packets
Link-state
RouterA sends its LSA headers, and RouterB compares the Update
neighbor’s headers with those in its own database. Packet
RouterB sends a Link State Request packet, requesting LSAs that

are not in its own database, and RouterA sends a Link State
Update packet containing its own self-originated Router LSA.
Link-state
R
Request t
Packet

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 RouterB

Link State Request Packet
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)
Area: 1.0.0.0
Link State Request Header:
LSA Type: Router LSA (1) RouterB includes header
10 1 0 25 information for the LSAs
Advertising Router: 10.1.0.25 required to synchronize its
LS Sequence Number: 80000000 database with RouterA.
…
Rev. 10.41 4-8

Technet24.ir

Link State Update Packet
Ethernet header:
Dest: <RouterB MAC> Source: <RouterA MAC>
IP datagram header:
Protocol: 89 (OSPF)
Source: 10.1.64.1
10 1 64 1 Dest: 10.1.64.2
10 1 64 2
OSPF Header:
OSPF Version: 2
Message Type: LS Update (4)
Area: 1.0.0.0 While the Database Description and Link
LS Update Packet: State Request packets include only LSA
Number of LSAs: 1 headers, the Link State Update packet
LS Type: Router-LSA provides detail about the advertising
Link State ID: 10.1.0.25 router’s connected networks.
Advertising Router: 10.1.0.25
10 1 0 25
LS Sequence Number: 80000000
Number of Links: 4

RouterA
VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
describes the contents of its link state database by
VLAN 64: 10.1.64.1/24
packets
RouterA sends its LSA headers, and RouterB compares the
neighbor’s headers with those in its own database.
RouterB sends a Link State Request packet, requesting LSAs that
are not in its own database, and RouterA sends a Link State
Update packet containing its own self-originated Router LSA.
Database synchronization occurs concurrently in both
directions during adjacency formation. RouterB describes its Link-state
database contents to RouterA.
RouterA RouterA requests LSAs
LSAs, and Acknowledgment
A k l d t
RouterB provides them. Packet
After both routers have explicitly acknowledged receipt of

the Link State Update packets, adjacency is complete. 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 RouterB
Rev. 10.41 4-9


Link State Acknowledgment Packet
Ethernet header:
Dest: <RouterA MAC> Source: <RouterB MAC>
IP datagram header:
Protocol: 89 (OSPF)
S
Source: 10 1 64 2 Dest:
10.1.64.2 D t 10.1.64.1
10 1 64 1
OSPF Header:
OSPF Version: 2
Message Type: LS Acknowledge (5)
Area: 1.0.0.0 Like the Link State Request, the
Link State Request Header: acknowledgment contains LSA header
LSA Type: Router LSA (1) information. If RouterA does not
Link State ID: 10.1.0.25 receive an acknowledgment, it will
Advertising Router: 10.1.0.25 retransmit the Link State Update.
LS S
Sequence N Number:
b 80000000
…
The Network LSA: 1

In this example, only two routers are connected over an
Ethernet network. However, Ethernet is considered a multi-
access network type, and this requires the election of a
Designated Router and Backup Designated Router. OSPF Area 1.0.0.0 Networks:
VLAN 10: 10.1.10.1/24 RouterA
You can issue CLI commands that will display the router’s role VLAN 20: 10.1.20.1/24 ID: 10.1.0.25
on a multi-access network. This information is also included in VLAN 64: 10.1.64.1/24
Loop
L 0: 10.1.0.25/32
0 10 1 0 25/32
Hello messages sent by any neighbor on the network.
Ethernet header:
Dest: 01005e-000005 Source: <RouterA MAC> Hello
IP datagram header:
Protocol: 89 (OSPF)
Source: 10.1.64.1 Dest: 224.0.0.5
OSPF Header:
OSPF Version: 2 Message g Type:
yp Hello p
packet (1)
( )
Area: 1.0.0.0 Hello
OSPF Hello Packet Header:
Network Mask: 255.255.255.0 OSPF Area 1.0.0.0 Networks:
Hello interval: 10 seconds ID: 10.1.0.26
VLAN 30: 10.1.30.1/24
Router Priority: 1 VLAN 40: 10.1.40.1/24
Router Dead Interval: 40 seconds RouterA is the VLAN 64: 10.1.64.2/24
Designated Router: 10.1.64.1 Designated Router Loop 0: 10.1.0.26/32 RouterB
Backup Designated Router: 10.1.64.2 for this network.
Active Neighbor: 10.1.0.26
Rev. 10.41 4 - 10
Technet24.ir
The Network LSA: 2

VLAN 10: 10.1.10.1/24 RouterA
on a multi-access network. This information is also included in VLAN 64: 10.1.64.1/24
Loop
L 0: 10.1.0.25/32
0 10 1 0 25/32
Hello messages sent by any neighbor on the network.
As soon as these routers have completed forming their
adjacency, the elected Designated Router (DR) generates
a second LSA type, known as a Network LSA.
Adjacent neighbors must always have synchronized link
state databases. This requirement causes the DR to
immediately send the new Network LSA to its neighbors.
OSPF Area 1.0.0.0 Networks:

ID: 10.1.0.26
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 RouterB
The Network LSA: 3

Router ID: 10.1.0.25 Area 1.0.0.0 Link State Database VLAN 10: 10.1.10.1/24 RouterA
Link State Advertisement Type: Router LSA (1) VLAN 64: 10.1.64.1/24
Linkon a ID:
State multi-access
10 1 0 25 network. This information is also included in
10.1.0.25 Loop
L 0: 10.1.0.25/32
0 10 1 0 25/32
Hello messages
Advertising sent by any neighbor on the network.
Router: 10.1.0.25
Number of Links: 4
As soon
Type: Stub as
(3) these routers
Link have completed
ID: 10.1.0.25 forming their
Link Data: 255.255.255.255 Metric: 1
adjacency,
Type: Stub (3) the elected Designated
Link ID: 10.1.10.0 LinkRouter (DR) generates
Data: 255.255.255.0 Metric: 1
Type: Stub (3)
a second Link ID:
LSA type, 10.1.20.0
known Link Data: 255.255.255.0
as a Network LSA. Metric: 1
Type: Transit (2) Link ID: 10.1.64.1 Link Data: 10.1.64.1 Metric: 1
LinkAdjacent
State Advertisement
neighbors Type:must
Router LSA (1)have synchronized link
always
state databases.
Advertising This requirement causes the DR to
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 Metric: 1
T
Type: St
Stubb (3) Li k ID
Link ID: 10
10.1.30.0
1 30 0 LinkLi k D
Data:
t 255
255.255.255.0
255 255 0 M ti 1
Metric:
Link State Advertisement Type: Network LSA (2)
Link State ID: 10.1.64.1 OSPF Area 1.0.0.0 Networks:
Advertising Router: 10.1.0.25 ID: 10.1.0.26
VLAN 30: 10.1.30.1/24
Netmask: 255.255.255.0 VLAN 40: 10.1.40.1/24
Attached Router: 10.1.0.25 VLAN 64: 10.1.64.2/24
Attached Router: 10.1.0.26 Loop 0: 10.1.0.26/32 RouterB
Rev. 10.41 4 - 11
Flooding LSAs in a Link State Update Packet: 1

RouterA and RouterB are adjacent, with three LSAs in their synchronized VLAN 10: 10.1.10.1/24
databases. When RouterB detects a new neighbor on one of its OSPF VLAN 20: 10.1.20.1/24
interfaces, the routers begin the exchange of messages that will VLAN 64: 10.1.64.1/24
Loop 0: 10.1.0.25/32
synchronize their link-state databases.
RouterA
ID: 10.1.0.25
Hello
DB Description
Link State Request
RouterC Link State Update RouterB
ID: 10.1.0.27
10 1 0 27 Li k St
Link State
t Ack
A k ID: 10.1.0.26
10 1 0 26
13 3
OSPF Area 1.0.0.0 Networks: OSPF Area 1.0.0.0 Networks:
VLAN 50: 10.1.30.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.40.1/24 VLAN 40: 10.1.40.1/24
VLAN 65: 10.1.65.1/24 VLAN 64: 10.1.64.2/24
Loop 0: 10.1.0.26/32 VLAN 65: 10.1.65.2/24
Loop 0: 10.1.0.26/32

Loop 0: 10.1.0.25/32
RouterA
g adjacency
RouterB’s existing j y with RouterA requires
q it to ID: 10.1.0.25
encapsulate any new LSAs in a Link State Update packet
that it floods immediately over the network they share. 3
RouterA does not request the new LSAs.
Hello
DB Description Link-state Update
Packet
Link State Request
ID: 10.1.0.27
10 1 0 27 Li k St
Link State
t Ack
A k ID: 10.1.0.26
10 1 0 26
16 16
VLAN 50: 10.1.30.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.40.1/24 VLAN 40: 10.1.40.1/24
VLAN 65: 10.1.65.1/24 VLAN 64: 10.1.64.2/24
Loop 0: 10.1.0.26/32 VLAN 65: 10.1.65.2/24
Loop 0: 10.1.0.26/32
Rev. 10.41 4 - 12
Technet24.ir

Loop 0: 10.1.0.25/32
RouterA
g adjacency
RouterB’s existing j y with RouterA requires
q it to ID: 10.1.0.25
encapsulate any new LSAs in a Link State Update packet
that it floods immediately over the network they share. 16
RouterA does not request the new LSAs.
After receipt of the new LSAs, each router Hello
updates its link-state database to include DB Description Link-state Update
them, and acknowledges their receipt. Packet
Link State Request
ID: 10.1.0.27
10 1 0 27 Li k St
Link State
t Ack
A k ID: 10.1.0.26
10 1 0 26
16 16
VLAN 50: 10.1.30.1/24 VLAN 30: 10.1.30.1/24
VLAN 60: 10.1.40.1/24 VLAN 40: 10.1.40.1/24
VLAN 65: 10.1.65.1/24 VLAN 64: 10.1.64.2/24
Loop 0: 10.1.0.26/32 VLAN 65: 10.1.65.2/24
Loop 0: 10.1.0.26/32
LSA Flooding in a Multi-access Network: 1

When an OSPF router experiences a link state transition, it must
originate a new instance of its Router LSA. The router floods the
advertisement to adjacent neighbors on point-to-point networks
using the reserved multicast address 224.0.0.5 (AllSPFRouters).
As each neighbor receives the LSA, it immediately floods to
adjacent
dj neighbors
i hb using
i the
h same multicast
li address.
dd Routers
R
do not flood LSAs onto networks without adjacent neighbors.
Rev. 10.41 4 - 13

DR
Multi-access
Multi access network
adjacent
dj neighbors
i hb using
i the
h same multicast
li address.
dd Routers
R Non-
do not flood LSAs onto networks without adjacent neighbors. DR 1
BDR
The multicast address to which LSAs are flooded on a multi- Non- Non-
access network depends on the state of the router interface DR 2 DR 3
flooding the advertisements.
• A non-Designated Router (non-DR) is adjacent to the DR and

Backup DR. It floods LSAs onto the multi-access network
g the multicast address 224.0.0.6 (AllDRouters). Onlyy
using
the DR and Backup DR process this update.

DR
Multi-access
Multi access network
adjacent
dj neighbors
i hb using
i the
h same multicast
li address.
dd Routers
R Non-
do not flood LSAs onto networks without adjacent neighbors. DR 1
BDR
The multicast address to which LSAs are flooded on a multi- Non- Non-
access network depends on the state of the router interface DR 2 DR 3
flooding the advertisements.
• A non-Designated Router (non-DR) is adjacent to the DR and

Backup DR. It floods LSAs onto the multi-access network
g the multicast address 224.0.0.6 (AllDRouters). Onlyy
using
the DR and Backup DR process this update.
• The DR is adjacent to all neighbors on the multi-access
network. It floods updates to the multicast address
224.0.0.5.
Rev. 10.41 4 - 14
Technet24.ir
Link State Advertisement Details: 1

OSPF routers run a link-state algorithm against their
Stub network Router ID: 10.1.0.32
database entries to create a graph that represents all 10.1.128.0/24 Int. s1: 10.1.4.1/30
routers and networks in the local OSPF area. Loop 0: 10.1.0.32/32
Int. e1: 10.1.128.1/24
Stub network
10.1.0.32/32
Each network’s type is important for graphing
Point-to-point network
purposes. The type of information included in a Router 10.1.4.0/30
LSA is unique for each type of network. Three of the
network types supported by OSPF are illustrated in Router ID: 10.1.0.33
Int. s1: 10.1.4.2/30
the graphic. Stub network Loop 0: 10.1.0.33/32
10.1.0.33/32 Int. e1: 10.1.64.1/24
• A point-to-point network is represented in the
Router LSA as Type 1. Transit network
10.1.64.0/24
• A transit network is a multi-access network Router ID: 10.1.0.34
with two or more connected routers. The Int. e1: 10.1.64.2/24 Router ID: 10.1.0.35
Int. e1: 10.1.64.3/24
Router LSA represents this network as Type 2. Loop 0: 10.1.0.34/32
Int. e2: 10.1.129.1/24 Loop 0: 10.1.0.35/32
Int. e2: 10.1.130.1/24
• A stub link can represent a multi-access
multi access Stub network Stub network
network, such as Ethernet, with only one 10.1.129.0/24 10.1.130.0/24
attached router. It is also used to represent the Stub network Stub network
router’s loopback interface. The Router LSA 10.1.0.34/32 10.1.0.35/32
represents stub networks as Type 3.
The DR for each multi-access transit network originates

a Network LSA that lists its connected routers.
Link State Advertisement Details: 2

Area 1.0.0.0 Link State Database
Router LSA (Type 1)
Link State ID: 10.1.0.32 Advertising Router: 10.1.0.32
Number of Links: 3
Type: Pt-to-Pt (1) Link ID: 10.1.0.33 Link Data: 10.1.4.1 Metric: 100
Router LSA (Type 1)
Number of Links: 3
Type: Pt-to-Pt (1) Link ID: 10.1.0.32 Link Data: 10.1.4.2 Metric: 100
Router LSA (Type 1)
Number of Links: 3
Router LSA (Type 1)
10 1 0 35 Advertising Router: 10.1.0.35
10 1 0 35
Number of Links: 3
Network LSA (Type 2)
Network Mask: 255.255.255.0
Attached Router: 10.1.0.35
Rev. 10.41 4 - 15
Relationship Between Updates and the IP Route Table

The relationship between OSPF link state updates and the IP route table is indirect.
1. OSPF routers originate link-state advertisements and flood them to adjacent neighbors
within link-state update packets, following the rules described earlier. The advertisements
are stored in a database.
2 Each router uses the database contents to create a graph that consists of vertices and
2.
edges.
• A “vertex” may be a router or a multi-access network with two or more connected
routers.
• An “edge” is a line connecting a pair of vertices.
3. Each router runs the link-state algorithm to create a tree containing all paths to each
destination network and router, placing itself at the root. It uses the metrics associated with
each path segment to calculate the shortest path to each destination.
4. Having derived the cumulative cost of the shortest path to each destination, the router
places the cost and next hop in its IP route table.
Link-State Shortest-path Route table

Graph
Database tree entries
Graphing Link State Advertisements: 1

The graph uses a one-way arrow
Stub link
10.1.128.0/24
Router: to represent stub networks.
10.1.0.32
Stub link It represents point-to-point
10.1.0.32/32 Stub link networks using two arrows. This
10.1.4.1/32
router represents its point-to-point
Router: link using an arrow that points to
10 1 0 33
10.1.0.33 th router
the t on ththe other
th side
id off th
the
Stub link link.
10.1.4.2/32
Router 10.1.0.33 represents its
own side of the point-to-point link
Network: using an arrow that connects to
10.1.64.3 Router 10.1.0.32.
Router 10.1.0.33’s loopback
OSPF does not require that point-to-point links be assigned an IP interface is shown as a stub
address. An unnumbered point-to-point network would be graphed as it network.
is currently shown. However, this example does assign address space
This router also has a connection
to the link,
link so our graph represents this address space as two stub links
links.
to a multi-access transit network.
Rev. 10.41 4 - 16
Technet24.ir

Stub link
Router:
10.1.128.0/24
10.1.0.32 The Designated Router of the
Stub link multi-access network originates
10.1.0.32/32 Stub link the Network LSA. The graph
10.1.4.1/32
includes an arrow from the
Router: Network vertex to the DR’s
10 1 0 33
10.1.0.33
vertex.
Stub link
Router: 10.1.4.2/32 The graph uses arrows to
10.1.0.34 represent other routers attached
to this network.
Network:
10.1.64.3
Router:
10.1.0.35

Stub link
Router:
10.1.128.0/24
10.1.0.32 The Designated Router of the
Stub link multi-access network originates
10.1.0.32/32 Stub link the Network LSA. The graph
10.1.4.1/32
includes an arrow from the
Router: Network vertex to the DR’s
10 1 0 33
10.1.0.33
vertex.
Stub link
Router: 10.1.4.2/32 The graph uses arrows to
10.1.0.34 represent other routers attached
to this network.
Network:
10.1.64.3 The networks connected to
routers 10.1.0.34 and 10.1.0.35
are graphed using the same
Router: procedure.
10.1.0.35
Rev. 10.41 4 - 17
OSPF Graph and Link State Database Entries

Routers internal to the same area have synchronized databases,
and this causes the routers to create the same graph.

Area ID Type Link State ID Router ID Sequence
1.0.0.0 Stub link 10.1.0.32 10.1.0.32 0x0
1000
1.0.0.0 Stub link 10 1 0 33
10.1.0.33 10 1 0 33
10.1.0.33 0x0
1.0.0.0 Stub link 10.1.0.34 10.1.0.34 0x0
1.0.0.0 Stub link 10.1.0.35 10.1.0.35 0x0
1.0.0.0 Stub link 10.1.4.0 10.1.0.32 0x0
1.0.0.0 Stub link 10.1.4.0 10.1.0.33 0x0
1.0.0.0 Stub link 10.1.128.0 10.1.0.32 0x0
1.0.0.0 Stub link 10.1.129.0 10.1.0.34 0x0
1.0.0.0 Stub link 10.1.130.0 10.1.0.35 0x0
1.0.0.0 Router link 10.1.0.32 10.1.0.32 0x80000008
1.0.0.0 Router link 10.1.0.33 10.1.0.33 0x80000009
1.0.0.0 Router link 10.1.0.34 10.1.0.34 0x80000006
1.0.0.0 Router link 10.1.0.35 10.1.0.35 0x80000013
1.0.0.0 Network link 10.1.64.3 10.1.0.35 0x80000008
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.
Populating the IP Route Table: 1

Each router uses the graph to create a tree, with itself
Router: 10.1.0.32
as the root, that specifies the shortest path to each
range of IP address space. Network10.1.128.0/24
The router populates its IP route table with the router

interface IP address that serves as the next hopp
R t 10.1.0.33
Router: 10 1 0 33
toward each destination.
Network10.1.64.0/24
Router: 10.1.0.34 Router: 10.1.0.35
Network10.1.129.0/24 Network10.1.130.0/24
Rev. 10.41 4 - 18
Technet24.ir
Populating the IP Route Table: 2
Fast convergence is one of OSPF’s 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
Adjacent
change in Location A. neighbors
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.
LSAs
Location C
Location A
address range:
address range:
10.3.0.0/16
10.1.0.0/16
Location B
address range:
10.2.0.0/16
LSAs and Remote Locations

As the number of routers that share a synchronized
database increases, it becomes more likely that one
or more of them could be experiencing link state
changes at any given time.
Increasing the size and complexity of the
shortest-path
h h tree is
i not, iin iitself,
lf a problem.
bl
OSPF was designed for large and complex
intranets.
The relative isolation of each location within this
intranet makes it unnecessary for routers at one
location to have detailed information about the
topology of remote locations. Link state changes
internal to one location will not change the next
hopp for anyy routers at other locations.
Rev. 10.41 4 - 20
Technet24.ir
OSPF Router Types:

Area Border Router
OSPF area border routers create boundaries for
the Router and Network LSAs that are flooded
Area 0.0.0.0 Area 0.0.0.3
within an area to maintain database
Area 0.0.0.1
synchronization.
One area within a multiple-area OSPF

Autonomous System must serve as the backbone.
The backbone area has the area ID 0.0.0.0.
Router connecting a non-

Area border router
backbone area to the backbone.
A
Area 0.0.0.2
0002
OSPF Router Types:

Internal Router
Area 0.0.0.0 Area 0.0.0.3
Area 0.0.0.1
synchronization.


Area border router
Router with all interfaces in the

Internal router
same area.
A
Area 0.0.0.2
0002
Rev. 10.41 4 - 21
OSPF Router Types:

Backbone Router
Area 0.0.0.0 Area 0.0.0.3
Area 0.0.0.1
synchronization.


Area border router
Internal router Router with all interfaces in the

same area.
Router
R t with
ith one or more A
Area 0.0.0.2
0002
Backbone router
interfaces in the backbone.
ABR Originates Summary LSAs

An area border router (ABR) has at least one
Router and Network LSAs flow over
interface in the backbone area, and at least one
adjacencies within the area
interface in a non-backbone area. An area may be
connected to the backbone by multiple ABRs;
however, there must be at least one ABR per area.
A ABR maintains
An i i adjacencies
dj i withi h neighbors
i hb iin each
h
area. These adjacencies enable the ABR to maintain
a synchronized copy of the link-state database for
Area 0.0.0.0
each area. ABR
This ABR originates a Summary LSA for each network Area 0.0.0.2
in the backbone, and floods these over adjacencies
with neighbors in the non-backbone area, which is
Area 0.0.0.2 in this example.
The ABR also
Th l originates a SSummary LSA ffor each
h
network in the non-backbone area (Area ID 0.0.0.2),
and floods these over adjacencies with neighbors in
the backbone.. Router and Network LSAs flow over
adjacencies within the area
Like all other LSA types, Summary LSAs are encapsulated
in Link State Update packets. A Link State Update packet
can contain LSAs of multiple types.
Rev. 10.41 4 - 22
Technet24.ir
Summary LSA Scope

While the scope of Router and Network LSAs is a single area, the
scope of Summary LSAs is the entire OSPF autonomous system.
Area 0.0.0.0
Summary LSAs from Area 0.0.0.2 Area 0.0.0.3
flow through the backbone into all
other non-backbone areas.
ABR
Summary LSAs
representing Area
Area 0.0.0.1 0.0.0.2 networks
ABR ABR
Area 0.0.0.2
Summary LSA Scope

While the scope of Router and Network LSAs is a single area, the
scope of Summary LSAs is the entire OSPF autonomous system.
Area 0.0.0.0
Summary LSAs from Area 0.0.0.2 Area 0.0.0.3
flow through the backbone into all
other non-backbone areas.
ABR
Summary LSAs
representing Area
Area 0.0.0.1 0.0.0.2 networks
ABR ABR
Area 0.0.0.2
Rev. 10.41 4 - 23
Summary LSAs Encapsulated in Link State Update Packet: 1
In this example, Router 10.1.0.32 is an

ABR that connects Area 0.0.0.1 to the
backbone. Area 0.0.0.0
g
The ABR originates one Summaryy LSA Router ID: 10.1.0.32
A
Area 0 0 0 0 interface:
0.0.0.0. i t f
for each network in the non-backbone Int. e2: 10.0.64.1/24
area and floods them over adjacencies Area 0.0.0.1 interfaces: Router ID: 10.1.0.33
Int. s1: unnumbered Area 0.0.0.1 interfaces:
in the backbone area. Int. s2: unnumbered Int. s1: unnumbered
Loop 0: 10.1.0.32/32 Int. s2: unnumbered
Int. e1: 10.1.128.1/24 Loop 0: 10.1.0.33/32
Int. e1: 10.1.129.1/24
Stub network Stub network
10.1.128.0/24 10.1.129.0/24
10.1.0.32/32 10.1.0.33/32
0 03
Router ID: 10.1.0.34 Router ID: 10.1.0.35
0 03
Area 0.0.0.1 interfaces: Area 0.0.0.1 interfaces:
Int. s1: unnumbered Int. s1: unnumbered
Loop 0: 10.1.0.34/32 Loop 0: 10.1.0.35/32
Int. e2: 10.1.130.1/24 Int. e2: 10.1.131.1/24
Area 0.0.0.1
10.1.130.0/24 10.1.131.0/24

10.1.0.34/32 10.1.0.35/32

Area ID Type Link State ID Router ID Sequence
0.0.0.1 Stub link 10.1.0.32 10.1.0.32 0x0
0 0 01
0.0.0.1 Stub link 10 1 0 33
10.1.0.33 10 1 0 33
10.1.0.33 0x0
0.0.0.1 Stub link 10.1.0.34 10.1.0.34 0x0
0.0.0.1 Stub link 10.1.0.35 10.1.0.35 0x0
0.0.0.1 Stub link 10.1.128.0 10.1.0.32 0x0
0.0.0.1 Stub link 10.1.129.0 10.1.0.33 0x0
0.0.0.1 Stub link 10.1.130.0 10.1.0.34 0x0
0.0.0.1 Stub link 10.1.131.0 10.1.0.35 0x0
0.0.0.1 Router link 10.1.0.32 10.1.0.32 0x80000008
0.0.0.1 Router link 10.1.0.33 10.1.0.33 0x80000009
0.0.0.1 Router link 10.1.0.34 10.1.0.34 0x80000006
0.0.0.1 Router link 10.1.0.35 10.1.0.35 0x80000013
Rev. 10.41 4 - 24
Technet24.ir

Link State Update Packet (flooded into Area 0.0.0.0)
OSPF Header
Link State Update Packet Number of LSAs: (8)
LSA Type: Summary-LSA (Type 3)
Link-State ID: 10.1.0.32 Advertising Router: 10.1.0.32
Netmask: 255.255.255.255
LSA Type:
yp Summary-LSA y ((Type
yp 3))
Netmask: 255.255.255.255
Netmask: 255.255.255.255
Netmask: 255.255.255.255
Netmask: 255.255.255.0
255 255 255 0
Netmask: 255.255.255.0
Netmask: 255.255.255.0
Netmask: 255.255.255.0
Multiple ABRs Each Send Summary LSAs: 1
For added resilience, OSPF areas may be

connected to the backbone by more than Area 0.0.0.0
one area border router. In this example,
both ABRs with Router IDs 10.1.0.32 and
Router ID: 10.1.0.32
10.1.0.33 connect Area 0.0.0.1 to the A
0.0.0.0. i t f
A
0.0.0.0. i t f
backbone. Int. e2: 10.0.64.1/24 Int. e2: 10.0.64.2/24
Int. s1: unnumbered
Each ABR advertises networks within Int. s1: unnumbered
Area 0.0.0.1 by originating Summary Loop 0: 10.1.0.32/32 Loop 0: 10.1.0.33/32
Int. e1: 10.1.128.1/24 Int. e1: 10.1.129.1/24
LSAs and flooding them into the
backbone area. Stub network Stub network
10.1.128.0/24 10.1.129.0/24
10.1.0.32/32 10.1.0.33/32
0 03
0 03
Loop 0: 10.1.0.34/32 Loop 0: 10.1.0.35/32
Int. e2: 10.1.130.1/24 Area 0.0.0.1 Int. e2: 10.1.131.1/24
10.1.130.0/24 10.1.131.0/24

10.1.0.34/32 10.1.0.35/32
Rev. 10.41 4 - 25
Multiple ABRs Each Send Summary LSAs: 2
For added resilience, OSPF areas may be

connected to the backbone by more than Area 0.0.0.0
one area border router. In this example,
both ABRs with Router IDs 10.1.0.32 and
10.1.0.33 connect Area 0.0.0.1 to the A
0.0.0.0. i t f
A
0.0.0.0. i t f
backbone. Int. e2: 10.0.64.1/24 Int. e2: 10.0.64.2/24
Int. s1: unnumbered
Each ABR advertises networks within Int. s1: unnumbered
Area 0.0.0.1 by originating Summary Loop 0: 10.1.0.32/32 Loop 0: 10.1.0.33/32
Int. e1: 10.1.128.1/24 Int. e1: 10.1.129.1/24
LSAs and flooding them into the
backbone area. Stub network Stub network
10.1.128.0/24 10.1.129.0/24
Area ID Type Link State ID Router ID Sequence 10.1.0.32/32 10.1.0.33/32
…
0 03
0 03
0.0.0.0 Summary 10.1.128.0 10.1.0.32 0x80000000
0.0.0.0 Summary 10.1.128.0 10.1.0.33 0x80000000
0.0.0.0 Summary 10.1.129.0 10.1.0.32 0x80000000
Loop 0: 10.1.0.34/32 Loop 0: 10.1.0.35/32
0.0.0.0 Summary 10.1.129.0 10.1.0.33 0x80000000
Int. e2: 10.1.130.1/24 Area 0.0.0.1 Int. e2: 10.1.131.1/24
0.0.0.0 Summary 10.1.130.0 10.1.0.32 0x80000000
0.0.0.0 Summary 10.1.130.0 10.1.0.33 0x80000000 10.1.130.0/24 10.1.131.0/24
0.0.0.0 Summary 10.1.131.0 10.1.0.32 0x80000000
0.0.0.0 Summary 10.1.131.0 10.1.0.33 0x80000000 10.1.0.34/32 10.1.0.35/32
…
Advertising Address Ranges Within Summary LSAs: 1
Without explicit configuration, ABRs

originate Summary LSAs for each Area 0.0.0.0
network. If IP address space has been
assigned hierarchically, following the
topology of the OSPF autonomous system, A
0.0.0.0. i t f
A
0.0.0.0. i t f
you can minimize the number of Summary Int. e2: 10.0.64.1/24 Int. e2: 10.0.64.2/24
LSAs by configuring address range Area 0.0.0.1 interfaces: Area 0.0.0.1 interfaces:
summarization. Int. s2: unnumbered Int. s2: unnumbered
Loop 0: 10.1.0.32/32 Loop 0: 10.1.0.33/32
Int. e1: 10.1.128.1/24 Int. e1: 10.1.129.1/24
When an ABR has been configured with
address range summarization, it will Stub network Stub network
advertise the entire address range with a 10.1.128.0/24 10.1.129.0/24
single Summary LSA. Stub network Stub network

10.1.0.32/32 10.1.0.33/32
0 03
0 03
Loop 0: 10.1.0.34/32 Loop 0: 10.1.0.35/32
Int. e2: 10.1.130.1/24 Area 0.0.0.1 Int. e2: 10.1.131.1/24
10.1.130.0/24 10.1.131.0/24

10.1.0.34/32 10.1.0.35/32
Rev. 10.41 4 - 26
Technet24.ir
Advertising Address Ranges Within Summary LSAs: 2
Redistributing Non-OSPF Network Information

OSPF routers advertise:
• Locally connected OSPF networks using

Router LSAs and Network LSAs Internet
• Networks in another area using Summary Area 0
LSAs (Backbone)
address
dd range:
Routing information that comes from a source 10.0.0.0/16
other than OSPF is considered “external”
Examples of external routing information include:
Area 2
• Default route to the Internet address range:
10.2.0.0/16
• Static route to portions of the intranet that do
not use OSPF
g
• Routes learned from RIP neighbors
RIP domain
Area 1
172.16.0.0/16
address range:
10.1.0.0/16
Rev. 10.41 4 - 27
Autonomous System Boundary Router (ASBR)
An Autonomous System Boundary Router (ASBR)

is an OSPF router that has learned routes from a
non-OSPF source and redistributes them into the
OSPF autonomous system. Area 0 Internet
(Backbone)
An ASBR generates one AS External LSA for address
dd range: ASBR
each non-OSPF network. However, routers 10.0.0.0/16
support definition of policies that summarize the
redistributed address space, which results in a
smaller number of AS External LSAs. Area 2
address range:
10.2.0.0/16
ASBR
RIP domain
Area 1
172.16.0.0/16
address range:
10.1.0.0/16
Normal and Stub Area Types

OSPF areas are divided into two main categories:
• Transit-type areas, such as the backbone area and Area
0.0.0.3 (which may be abbreviated to “3”), can carry traffic
Internet
that whose source or destination is outside the area. One
sub-type of transit area is configured as “normal.”
ASBR
• Stub-type areas, such as Area 1 and Area 2, carry Area 0.0.0.0
only traffic whose source or destination is within (Normal)
the area.
Traffic destined for the
The ASBR in the backbone area uses RIP domain travels
a static route to provide Internet Area 0.0.0.1 through this area.
access. It converts the static route (Stub)
Area 0.0.0.3
into an AS External (Type 5) LSA,
(Normal)
and floods it into the backbone area. Area 0.0.0.2
(Stub) ASBR
The ABR for Area 3 floods the AS External
LSAs over adjacencies into Area 3. RIP domain
(172.16.0.0/16)
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
Technet24.ir
Main Benefit of Stub Area Definition

The benefit of the stub-type area definition becomes most
apparent in advertisements of the RIP networks in our example.
The ASBR within Area 3 has RIP interfaces and OSPF interfaces.
Internet
It converts RIP routes from its IP route table into one or more AS
External LSAs, and floods them to neighbors within Area 3.
ASBR
h AS Externall LSAs are flooded
The fl d d into the
h bbackbone.
kb Area 0
A 0.0.0.0
000
(Normal)
ABRs connecting stub areas, such
as Area 1 and Area 2, inject the
default route to represent all routes Area 0.0.0.1
external to OSPF, regardless of their (Stub)
Area 0.0.0.3
original source.
(Normal)
This technique minimizes unnecessary Area 0.0.0.2
(Stub) ASBR
information in the link-state database and
route tables
bl off OSPF routers internall to the
h
RIP domain
stub area. (172.16.0.0/16)
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.
Not-So-Stubby Area Type

Non-OSPF
An area that supports an ASBR, such as Area 3, cannot be domain
defined as a “stub” area type. However, it can have the
address summarization benefits of a stub area if it defined Internet
as a “not-so-stubby area” (NSSA). ASBR
In this example, an ASBR connected to the backbone ASBR
h severall static routes to address
has dd space outside
d the
h Area 0
A 0.0.0.0
000
(Normal)
OSPF domain.
The ASBR originates Type 5
External LSAs and floods them Area 0.0.0.1
into the backbone. (Stub)
Area 0.0.0.3
If Area 3 is defined as a NSSA area (NSSA)
type, its ABR will handle Type 5 AS Area 0.0.0.2
External LSAs the same as ABRs (Stub) ASBR
connectedt d tto stub
t b areas 1 and
d22. It will
ill
inject the default route in place of the RIP domain
(172.16.0.0/16)
External LSAs.
Rev. 10.41 4 - 29
The NSSA Link State Advertisement

Type 5 AS External LSAs cannot exist within a “Stub” or “NSSA” area type. The change in Area
3’s status from “Normal” to “NSSA” affects the method its ASBR will use to advertise its external
RIP routes.
The ASBR within Area 3 advertises the non-OSPF networks using a Type 7 NSSA LSA.
The ABR that connects Area 3 to the backbone translates the Type 7
LSAs into Type 5 LSAs and floods them into the backbone, at which
Internet
point they are handled as described earlier.
ASBR
Area 0.0.0.0
(Normal) ABR for a NSSA-type area
converts Type 7 LSAs to AS
External (Type 5) LSAs.
ABR
Area 0.0.0.1
(Stub) ASBR within a stub area
Area 0.0.0.3 advertises external routes by
(NSSA) originating NSSA (Type 7) LSAs
Area 0.0.0.2
ASBR
(Stub)
RIP domain
(172.16.0.0/16)
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 theyy 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
Technet24.ir
HP Switching and Routing Technologies IP Multicast Protocols
Module 5: IP Multicast Protocols

Objectives
• Articulate the advantages of using IP multicast technology to deliver multimedia traffic streams.
• Identify the roles of IGMP and PIM in multicast communications, and the scope of each
protocol.
protocol
• Describe the operation of PIM Dense and PIM Sparse and their appropriate network
deployments.
A server sending video traffic to specific receivers over 10.4.110.145/24 10.4.110.150/24

IP networks has a choice among communication
methods. Each method produces a unique result.
An individual copy of each video frame is
Unicast Multiple copies of
sent to each receiver.
eachh frame
f may
increase traffic
congestion
10.4.32.50/24
/
10.4.10.10/24
The server will

support a limited
number of receivers.
10.4.10.50/24
Rev. 10.41 5-1

A server sending video traffic to specific receivers over

An individual copy of each video frame is 10.4.110.145/24 10.4.110.150/24
Unicast
A single copy of each video frame is sent
Broadcast to the all hosts broadcast address. The router drops
broadcast traffic,
making this a
local-only solution.
10.4.32.50/24
The layer 2 switch floods

broadcast traffic over all
links potentially
links, /
10.4.10.10/24
overwhelming some hosts
with unwanted traffic.
10.4.10.50/24
A server sending video traffic to specific receivers over

An individual copy of each video frame is 10.4.110.145/24 10.4.110.150/24
Unicast
Broadcast to the all hosts broadcast address.
Multicast
to an IP multicast address.
10.4.32.50/24
Multicast combines the benefits of the Layer 2 and Layer 3

other methods, while eliminating their devices, when configured
disadvantages. to support IP multicast,
will forward the traffic
onlyy toward
w receivers.
v /
10.4.10.10/24
10.4.10.50/24
Rev. 10.41 5-2

Technet24.ir
Multicast Addresses
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
Class D
224-239
use within an enterprise:
Class C • 239.0.0.0 – 239.255.255.255
192-223
Class B
128-192
Class A
0-127
Resolving IP Multicast to Ethernet Addresses
IP multicast addresses (224.0.0.0 – 239.255.255.255) map directly to

Ethernet multicast addresses: 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
Hexadecimal 01005e - 00 00 05
zero in the most significant position
Binary 0000 0 001 0000 0000 0101 1110
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

Multicast Protocol Scopes: 1
When senders and receivers are located on

different networks, IP multicast requires the
interaction of at least two protocols.
IGMP IGMP
IGMP IGMP
PIM
Multicast Protocol Scopes: 2
When senders and receivers are located on Group

member
different networks, IP multicast requires the
interaction of at least two protocols.
The
h Internet Group Management Protocoll
(IGMP) runs at the network edge. Routers and
switches exchange IGMP messages with IP
IGMP IGMP
hosts, and direct the multicast stream on to
network segments that contain group members.
Routers use a multicast routing protocol, such as

Protocol Independent Multicast (PIM), to
maintain the distribution tree that carries traffic IGMP IGMP
PIM
from its source to networks with group members.
Group Source
members
Rev. 10.41 5-4

Technet24.ir
Roles of Multicast-Capable Devices

An IGMP Querier is a device that sends An IGMP host is an end station that runs
periodic messages to a multicast address. multicast applications, enabling it to
The Querier, which is usually a router, respond to the periodic messages sent by
maintains tables that determine which of the Querier.
its interfaces lead to receivers of multicast
traffic
traffic. IGMP messages originated by the host
enable it to signal its intention to receive,
Each multicast-enabled broadcast
IGMP Querier or stop receiving, a multicast data stream.
domain must have one active Querier
and possibly a backup Querier.
Router int. 1: Router int. 2:
10.1.4.1/24 10.1.8.1/24
IGMP hosts
.11 .12 .13 .14 .11 .12 .13 .14
Network 10.1.4.0/24 Network 10.1.8.0/24
IGMP General Query: 1
In its role as the IGMP Querier, this router sends

periodic Host Membership Requests through its
IGMP-enabled interfaces.
The Querier continues to send the General

Query regardless of whether any multicast
Query,
traffic actually being transmitted.
Int. 1: Int. 2:
10.1.4.1/24 10.1.8.1/24
The Layer 2 switches flood the

request through all ports.
.11 .12 .13 .14 .11 .12 .13 .14
Network 10.1.4.0/24 Network 10.1.8.0/24
Rev. 10.41 5-5

IGMP General Query: 2
Ethernet header:
Dest: 01:00:5e:00:00:01 Source: <Router_MAC>
Type: IP (0x0800)
The multicast address
IP datagram header: 224.0.0.1 includes all
Protocol: IGMP (0x02) IP hosts.
h
Source: 10.1.4.1 Destination: 224.0.0.1
Internet Group Management Protocol:

IGMP Version: 2
Type: Membership Query (0x11) This is a type of Host Membership
Max Response Time: 10.0 sec Request which is known as a General
Multicast Address: 0.0.0.0 Query. The default interval between
General Queries is 125 seconds.
IGMP Host Membership Report: 1

Hosts originate a Membership Report when There are several ways in which a multicast client
an IGMP-compatible multicast receiver application may obtain the appropriate group address,
application is launched. This message including:
enables the host to join a multicast group.
• Hard-code the multicast address
An IGMP host can join a group regardless
• Prompt
p the user to p
provide the address
of whether the source for this group has
begun to transmit data. • Dynamically obtain the address from a server
Querier
Int. 1: Int. 2:
10.1.4.1/24 10.1.8.1/24
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 .11 .12 .13 .14
Network 10.1.4.0/24 Network 10.1.8.0/24
Rev. 10.41 5-6

Technet24.ir
IGMP Host Membership Report: 2
Ethernet header:
Dest: 01:00:5e:40:0c:2a Source: <Host_MAC>
Type: IP (0x0800)
The IP destination of the
IP datagram header: Membership Report is the address
Protocol: IGMP (0x02) off the
h multicast
li group the
h IGMP
Source: 10.1.4.11 Dest: 239.192.12.42 Host wants to join.
Internet Group Management Protocol:

IGMP Version: 2
Type: Membership Report (0x16) The IGMP host uses this message to
Max Response Time: 0.0 sec signal its intent to receive a specific
Multicast Address: 239.192.12.42 multicast stream.
Router Forwards Multicast Traffic

On receipt of the Membership Report, the router creates an IGMP table entry associating the multicast
group address with Int. 1, which is the port leading toward group members.
When the data stream associated with this multicast group begins,
the router will forward the traffic through its interface 1.
Int. 3: 10.1.16.128/24
10.1.16.1/24
Int. 1: Int. 2:
10.1.4.1/24 10.1.8.1/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

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 non-
member ports based on detection of
Membership Reports sent by group members in IGMP-snooping switches respond to
response to Membership Requests. additional membership reports by
forwarding the traffic toward group
members.
Int. 1: Querier Int. 2:
10.1.4.1/24 10.1.8.1/24
Group
members
.11 .12 .13 .14 .11 .12 .13 .14
Network 10.1.4.0/24 Network 10.1.8.0/24
IP Multicast With a Layer 3 Switch

When IGMP runs on a Layer 3 switch that uses
VLAN interfaces, IGMP and PIM are enabled
within VLAN interfaces.
In this example, all members of the multicast group
are connected to the same router. The router uses
PIM to associate the source of multicast traffic with
the group address to which it transmits traffic.
The Layer 3 switch filters or forwards the traffic
based on messages from IGMP hosts. 10.1.16.128/24
VLAN 16 interface: Source of multicast group
239.192.12.42
10.1.16.1/24
IGMP and PIM enabled
VLAN 4 interface: VLAN 8 interface:

10.1.4.1/24 10.1.8.1/24
IGMP and PIM enabled IGMP and PIM enabled
.11 .12 .13 .14 .11 .12 .13 .14

Members of multicast Members of multicast
group 239.192.12.42 group 239.192.12.42
Rev. 10.41 5-8

Technet24.ir
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 Source
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.
Group Group Group
– Nodes without group presence or members members members
downstream neighbors are not part of the
distribution tree.
Comparing PIM Dense and Sparse Modes
Like unicast routing protocols, multicast routing protocols exchange period messages with neighbors to
build a multicast distribution tree.
Dense and sparse mode protocols approach this challenge from opposite perspectives, as outlined in the
chart. This lesson provides more information on dense and sparse modes of Protocol Independent Multicast.
How the distribution Multicast group/distribution

Use model
tree is built tree relationship
PIM Dense Mode Senders and receivers are Multicast traffic is initially flooded to Routers dynamically create a
(PIM-DM) located in close proximity, all nodes, who eventually prune distribution tree for each multicast
or connected by links with themselves from the tree if they have group.
plentiful bandwidth. no downstream group members.
PIM Sparse Mode Senders and receivers are On protocol startup, one node is Routers define a shared tree that
(PIM SM)
(PIM-SM) separated by distance
distance, or identified as the root of the tree
tree. can carry traffic for multiple
connected by lower- Routers explicitly request the stream if groups.
bandwidth point-to-point they have downstream group
links. members.
Rev. 10.41 5-9

PIM Neighbor Discovery
Each PIM router begins neighbor detection as Refer to next page to view the Hello
soon as the protocol becomes active. It message Router 1 sends over this link.
originates a Hello message for each interface
and sends it on a configurable interval.
PIM routers store neighbor
g identities in a
table.
The format of Hello messages is the Router 1: Router 2:
same whether originated by PIM dense Int 1: 10.1.4.1/24 1 1 Int 1: 10.1.5.1/24
Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
or sparse mode routers. However, routers
Int 3: 10.1.65.1/24 Int 3: 10.1.66.1/24
that share a network must be using the Int 4: 10.1.68.1/24 3 4 4 3 Int 4: 10.1.67.1/24
same mode if they are to become
neighbors.
Router 3: 2 2 Router 4:
Int 1: 10.1.6.1/24 3 3 Int 1: 10.1.7.1/24
Int
I t 2: 10.1.65.2/24
2 10 1 65 2/24 I 2:
Int 2 10
10.1.66.2/24
1 66 2/24
Int 3: 10.1.67.2/24 1
Int 3: 10.1.68.2/24
1
PIM Neighbor Discovery:

Hello message
Ethernet header:
Dest: 01:00:5e:00:00:0d Source: <Router_MAC>
Type: IP (0x0800)
IP datagram header: PIM routers are members of the

Protocol: PIM (0x67) (Decimal: 103) multicast group 224.0.0.13.
Protocol Independent Multicast header:

Version: 2 PIM routers use Hello messages to discover
Type: Hello neighbors and negotiate parameters for their
PIM parameters: relationship. The “Holdtime” parameter
Holdtime: 105 sec states the amount of time the neighbor
should consider this router’s state to be valid.
Rev. 10.41 5 - 10
Technet24.ir
PIM Router Initial Flooding
Source:
When the server begins sending a multicast 10.1.5.37/24
stream, source node creates an entry in its PIM
route table containing the source and group
addresses.
Router 2:
The
Th source node d then
h flfloods
d the
h stream over R t 1
Router 1:
1 1
Int 1: 10.1.5.1/24
Int 1: 10.1.4.1/24
all other interfaces. This enables downstream Int 2: 10.1.64.1/24 2 2
Int 2: 10.1.64.2/24
Int 3: 10.1.66.1/24
routers to place the appropriate S,G pair in Int 3: 10.1.65.1/24 Int 4: 10.1.67.1/24
their PIM route tables. Int 4: 10.1.68.1/24 3 4 4 3
Each router floods the stream toward its PIM

neighbors. Depending on its IGMP Router 4:
Router 3: 2
implementation, a router or routing switch Int 1: 10.1.6.1/24
2 Int 1: 10.1.7.1/24
3 3
may also flood the multicast traffic on to user Int 2: 10.1.65.2/24
Int 2: 10.1.66.2/24
Int 3: 10.1.68.2/24
networks for the benefit of IGMP snooping Int 3: 10.1.67.2/24
1
1
Layer
y 2 switches.
PIM Router Initial Flooding:

Router 2 PIM Route Table and IP Route Table
The multicast data stream is uniquely identified by the The metric in this table corresponds
Source of the multicast traffic and its Group, which is with the metric associated with the
also known as an S,G pair. source network in the IP route table.
PIM Route Table: Router 2
Group Address Source Address Metric Metric Pref

--------------- --------------- ------------ ----------------
239.192.12.42 10.1.5.37 1 0
Source = 10.1.5.37
Group = 239.192.12.42
IP Route Table: Router 2

Destination Gateway Type Metric Distance
------------- ------------ ----------- -------- --------
10.1.4.0/24 10.1.64.1 ospf 109 110
10.1.5.0/24 connected 1 0
10.1.6.0/24 10.1.67.2 ospf 110 110
10.1.7.0/24 10.1.66.2 ospf 110 110
10.1.64.0/24 connected 1 0
10.1.65.0/24 10.1.64.1 ospf 19 110
10.1.66.0/24 connected 1 0
10.1.67.0/24 connected 1 0
10.1.68.0/24 10.1.64.1 ospf 19 110
Rev. 10.41 5 - 11


--------------- --------------- ------------ ----------------
239.192.12.42 10.1.5.37 109 110

Router 1’s upstream PIM neighbor is
------------- ------------ ----------- -------- --------
10.1.4.0/24 connected 1 0 10.1.64.2, which is its next hop to
10.1.5.0/24 10.1.64.2 ospf 109 110 reach the source network for this
10.1.6.0/24 10.1.65.2 ospf 110 110 multicast group. This router’s
10.1.7.0/24 10.1.68.2 ospf 110 110 “upstream interface,” or “reverse path
10.1.64.0/24 connected 1 0 interface” is 10.1.64.1.
10 1 65 0/24
10.1.65.0/24 connected
t d 1 0
10.1.66.0/24 10.1.64.2 ospf 19 110
10.1.67.0/24 10.1.64.2 ospf 19 110
10.1.68.0/24 connected 1 0


--------------- --------------- ------------ ----------------
239.192.12.42 10.1.5.37 110 110

------------- ------------ ----------- -------- --------
10.1.4.0/24 10.1.65.1 ospf 109 110 This router’s upstream PIM neighbor is
10.1.5.0/24 10.1.67.1 ospf 110 110 10.1.67.1. Its reverse path interface is
10.1.6.0/24 connected 1 0 10.1.67.2.
10.1.7.0/24 10.1.65.1 ospf 119 110
10.1.64.0/24 10.1.65.1 ospf 18 110
10 1 65 0/24
10.1.65.0/24 connected 1 0
10.1.66.0/24 10.1.65.1 ospf 29 110
10.1.67.0/24 connected 1 0
10.1.68.0/24 10.1.65.1 ospf 19 110
Rev. 10.41 5 - 12
Technet24.ir


--------------- --------------- ------------ ----------------
239.192.12.42 10.1.5.37 109 110

------------- ------------ ----------- -------- --------
10.1.4.0/24 10.1.66.1 ospf 110 110 This router’s upstream PIM neighbor is
10.1.5.0/24 10.1.66.1 ospf 109 110 10.1.66.1. Its reverse path interface is
10.1.6.0/24 10.1.68.1 ospf 119 110 10.1.66.2.
10.1.7.0/24 connected 1 0
10.1.64.0/24 10.1.66.1 ospf 18 110
10 1 65 0/24
10.1.65.0/24 10 1 68 1
10.1.68.1 ospf
f 19 110
10.1.66.0/24 connected 29 110
10.1.67.0/24 10.1.66.1 ospf 19 0
10.1.68.0/24 connected 19 110
PIM Loop Prevention 1
Source:
PIM-Dense routers obey the rule of “Reverse 10.1.5.37/24
Path Forwarding” to prevent loops during the
initial flood of multicast traffic.
Each router floods multicast traffic that arrives Router 1: Router 2:
through its reverse path interface. It filters Int 1: 10.1.4.1/24 1 1 Int 1: 10.1.5.1/24
multicast traffic that arrives through other Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
Int 3: 10.1.65.1/24 Int 3: 10.1.66.1/24
interfaces. Int 4: 10.1.68.1/24 Int 4: 10.1.67.1/24
3 4 4 3
As the source node, Router 2 floods the
multicast traffic over its PIM-enabled interfaces.
2 2
Int 1: 10.1.6.1/24 Int 1: 10.1.7.1/24
Int 2: 10.1.65.2/24 Int 2: 10.1.66.2/24
Int 3: 10.1.67.2/24 1 1 Int 3: 10.1.68.2/24
Reverse Path
interface
Filtered interface
Rev. 10.41 5 - 13
PIM Loop Prevention 2

Source:
10.1.5.37/24
Router 1 floods the traffic it receives through

its interface to the network it shares with
Router 2. Router 1: Router 2:
Int 1: 10.1.4.1/24 1 1 Int 1: 10.1.5.1/24
Routers 3 and 4 flood the multicast traffic Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
Int
I 3: 10.1.65.1/24
3 10 1 65 1/24 Int
I 3: 10.1.66.1/24
3 10 1 66 1/24
they receive through their reverse path Int 4: 10.1.68.1/24 Int 4: 10.1.67.1/24
interfaces. 3 4 4 3
The routers discard traffic they receive through

filtered interfaces. 2
2
Router 3: 3 Router 4:
HP networking E-series routing switches that Int 1: 10.1.6.1/24
3
Int 1: 10.1.7.1/24
implement Data-Driven IGMP will forward the Int 2: 10.1.65.2/24 Int 2: 10.1.66.2/24
traffic on to user networks only after IGMP Int 3: 10.1.67.2/24 1 1 Int 3: 10.1.68.2/24
hosts have joined the multicast group. Reverse Path interface
Filtered interface
Pruning Branches From the Distribution Tree
Source:
Populating the PIM route table is the primary 10.1.5.37/24
reason for the initial flood of multicast traffic.
PIM-Dense uses a multicast distribution model
known as “flood and prune.” After the initial Router 1: Router 2:
flood
fl d off traffic,
ffi a router b
begins
i to prune allll Int
I 1: 10.1.4.1/24
1 10 1 4 1/24 1 1 Int
I 1: 10.1.5.1/24
1 10 1 5 1/24
Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
branches other than those leading to Int 3: 10.1.65.1/24 Int 3: 10.1.66.1/24
downstream group presence. Int 4: 10.1.68.1/24 Int 4: 10.1.67.1/24
3 4 4 3
The routers initially begin by pruning the
redundant links.
2 2
Int 1: 10.1.6.1/24 Int 1: 10.1.7.1/24
Int 2: 10.1.65.2/24 Int 2: 10.1.66.2/24
Int 3: 10.1.67.2/24 1 1 Int 3: 10.1.68.2/24
Reverse Path interface

Filtered interface
Rev. 10.41 5 - 14
Technet24.ir
Pruning Routers From the Distribution Tree
Source:
IGMP Host
10.1.5.37/24
Membership Report
Router 1: Router 2:
Int 1: 10.1.4.1/24 1 Int 1: 10.1.5.1/24
.11 .12 .13 .14 1
Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
Int 3: 10.1.65.1/24 Int 3: 10.1.66.1/24
Group members: Int 4: 10.1.68.1/24 Int 4: 10.1.67.1/24
S: 10.1.5.37 3 4 4 3
G: 239.192.12.42 PIM Prune
message
2
Int 1: 10.1.6.1/24 Int 1: 10.1.7.1/24
3 3
Int 2: 10.1.65.2/24 Int 2: 10.1.66.2/24
In its role as IGMP Querier, each router Int 3: 10.1.67.2/24 Int 3: 10.1.68.2/24
maintains tables that determine whether its user 1 1
VLANs contain group members
members.
Router 1 remains a part of the distribution tree
for this multicast group due to downstream No group No group
group presence. members members
Based on lack of group presence, Routers 3 and 4 each

send a PIM Prune message to upstream neighbors.
Pruning Routers From the Distribution Tree:

PIM Prune Message
Ethernet header:
Dest: 01:00:5e:00:00:0d Source: <Router_3_MAC>
Type: IP (0x0800) The Prune message is sent to the PIM reserved multicast
address
address.
IP datagram header:
Protocol: PIM (0x67) (Decimal: 103)
This message format is used for the Prune message as
Source: 10.1.67.2 Destination: 224.0.0.13 well as a Join message used by PIM Sparse.
Version: 2 On a multi-access network, this PIM router may have
Type: Join/Prune (3) multiple upstream neighbors. The message specifies
PIM parameters: the upstream neighbor to which this message applies.
Upstream Neighbor: 10.1.67.1
Groups: 1 This distribution tree carries the data stream for a
H ld
Holdtime: 121 (sec)
( ) single multicast group. However, this message could
Group 0: 239.192.12.42/32 include information relating to multiple groups.
Join: 0
Prune: 1
The message specifies the multicast source whose
IP address: 10.1.5.37
data stream should be pruned.
Rev. 10.41 5 - 15
Graft Based on Downstream Group Presence: 1
Source:
10.1.5.37/24
Group members:
Router 1: Router 2:
S: 10
10.1.5.37
1 5 37 IIntt 1: 10.1.4.1/24
1 10 1 4 1/24 Int
I t 1: 10.1.5.1/24
1 10 1 5 1/24
1 1
G: 239.192.12.42 .11 .12 .13 .14 Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
Int 3: 10.1.65.1/24 Int 3: 10.1.66.1/24
Int 4: 10.1.68.1/24 Int 4: 10.1.67.1/24
Router 2 maintains the “prune” state for its 4
4 3
downstream neighbors, Router 3 and Router 4, PIM Graft
until they send a message changing the state. message
Router 3: Router 4:
When Router 3’s IGMP tables indicate group Int 1: 10.1.6.1/24
2
Int 1: 10.1.7.1/24
3
presence, it sends a PIM Graft message Int 2: 10.1.65.2/24
3
Int 2: 10.1.66.2/24
upstream. Int 3: 10.1.67.2/24 Int 3: 10.1.68.2/24
1 1
No group
Group members: members
IGMP Host
S: 10.1.5.37
Membership Report
.11 .12 .13 .14 G: 239.192.12.42

PIM Graft Message
Ethernet header:
Dest: <Router_2_MAC> Source: <Router_3_MAC>
Type: IP (0x0800)
The target of a PIM Graft message is a specific
IP datagram header: neighbor instead of the PIM reserved multicast
Protocol: PIM (0x67) (Decimal: 103) address.
dd

Version: 2
Type: Graft (6)
PIM parameters:
Upstream Neighbor: 10.1.67.1
Groups: 1
Holdtime: 0 (sec)
G
Group 0 239.192.12.42/32
0: 239 192 12 42/32
Join: 1 A PIM Graft message sets the Join field at 1 and the
IP address: 10.1.5.37 Prune field at 0. Like the Prune message, it specifies
Prune: 0 the distribution tree’s source and group addresses.
Rev. 10.41 5 - 16
Technet24.ir
Source:
10.1.5.37/24
Group members:
Router 1: Router 2:
S: 10
10.1.5.37
1 5 37 IIntt 1: 10.1.4.1/24
1 10 1 4 1/24 Int
I t 1: 10.1.5.1/24
1 10 1 5 1/24
1 1
G: 239.192.12.42 .11 .12 .13 .14 Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
Int 3: 10.1.65.1/24 Int 3: 10.1.66.1/24
Int 4: 10.1.68.1/24 Int 4: 10.1.67.1/24
Router 2 maintains the “prune” state for its 4 4 3
3
downstream neighbors, Router 3 and Router 4,
PIM Graft
until they send a message changing the state. Acknowledgment
Router 3: Router 4:
When Router 3’s IGMP tables indicate group Int 1: 10.1.6.1/24
2 2
Int 1: 10.1.7.1/24
3
presence, it sends a PIM Graft message Int 2: 10.1.65.2/24
3
Int 2: 10.1.66.2/24
upstream. Int 3: 10.1.67.2/24 Int 3: 10.1.68.2/24
1 1
Router 2 acknowledges
th G
the Graft
ft message.
No group
IGMP Host
S: 10.1.5.37
Membership Report
.11 .12 .13 .14 G: 239.192.12.42

PIM Graft Acknowledgment
Ethernet header:
Dest: <Router_3_MAC> Source: <Router_2_MAC>
Type: IP (0x0800)
The
e router
ou e receiving
ece v g a PIM
MG Graft
a message
essage from
o a
IP datagram header: downstream neighbor sends a Graft Acknowledgment
Protocol: PIM (0x67) (Decimal: 103) before sending the data stream.

Version: 2
Type: Graft-Ack (7)
PIM parameters:
Groups: 0
Rev. 10.41 5 - 17
PIM Prune Based on Loss of Group Presence: 1
Source:
10.1.5.37/24
Group members:
Router
R 1:
1 Router
R 2:
2
S: 10.1.5.37 Int 1: 10.1.4.1/24 Int 1: 10.1.5.1/24
1 1
G: 239.192.12.42 .11 .12 .13 .14 Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
Int 3: 10.1.65.1/24 Int 3: 10.1.66.1/24
Int 4: 10.1.68.1/24 Int 4: 10.1.67.1/24
Router 1 and Router 3 remain on the distribution 4 4 3
3
tree as long as each has at least one group
member on its user network.
2
Int 1: 10.1.6.1/24 3 Int 1: 10.1.7.1/24
3
Int 2: 10.1.65.2/24 Int 2: 10.1.66.2/24
Int 3: 10.1.67.2/24 Int 3: 10.1.68.2/24
1 1
No group
S: 10.1.5.37
.11 .12 .13 .14 G: 239.192.12.42
PIM Prune Based on Loss of Group Presence: 2
Source:
IGMP Leave Group 10.1.5.37/24
Group members: PIM Prune

Router
R 1:
1 Router
R 2:
2
S: 10.1.5.37 Int 1: 10.1.4.1/24
message Int 1: 10.1.5.1/24
1 1
G: 239.192.12.42 .11 .12 .13 .14 Int 2: 10.1.64.1/24 2 2 Int 2: 10.1.64.2/24
Int 3: 10.1.65.1/24 Int 3: 10.1.66.1/24
Int 4: 10.1.68.1/24 Int 4: 10.1.67.1/24
Router 1 and Router 3 remain on the distribution 4 4 3
3
tree as long as each has at least one group
member on its user network.
Router 3: Router 4:
When the last member on Router 1’s user Int 1: 10.1.6.1/24
2 2
Int 1: 10.1.7.1/24
3
network leaves the group, the router prunes itself Int 2: 10.1.65.2/24
3
Int 2: 10.1.66.2/24
from the tree. Int 3: 10.1.67.2/24 Int 3: 10.1.68.2/24
1 1
No group
S: 10.1.5.37
.11 .12 .13 .14 G: 239.192.12.42
Rev. 10.41 5 - 18
Technet24.ir
PIM Sparse Multicast Traffic Distribution
The flood and prune multicast traffic distribution method

employed by PIM Dense is appropriate in environments
R7
that provide plentiful bandwidth.
PIM Sparse may be more suitable in environments where
group members are widely dispersed, or connected by
l
lower-bandwidth
b d d h llinks.
k
PIM Join
The primary difference between PIM Dense and Sparse
modes is the way routers build distribution trees. R1 R2 R5
• A single distribution tree carries traffic for all groups.
• The source node of the tree may be statically defined. PIM Join
• Multicast traffic is never flooded downstream. R3 R4 R6

• PIM Sparse nodes forward the traffic only after they
receive an explicit Join request from a downstream IGMP Join
neighbor.
PIM-SM routers use Hello messages to set up neighbor Multicast group
members
relationships with other PIM routers.
PIM Sparse Terminology

A PIM-SM domain consists of a group of
interconnected routers running the PIM Sparse
Mode protocol. PIM-SM Domain
BSR for the domain
A Rendezvous Point (RP) acts as the root node
RP for 239.192.0.0/10
of the distribution tree for one or more Server 1: R7
multicast g p
groups. S: 10.1.5.17
10.1.5.17
10
G: 1
230.64.11.37
230
5 17
64 11 37
• Routers suitably located may be
10.1.5.3
configured as RP Candidates (RP-C) for
all or some portion of the multicast
RP for 239.64.0.0/10
address range.
A Bootstrap Router (BSR) distributes RP-to- R1 R2 R5
.1
Group mappings. A domain requires one
dynamically elected BSR. 10.1.5.0/24
PIM Join
Each network supports a Designated Router DR for Network
.2
(DR)
(DR). 10 1 5 0/24
10.1.5.0/24 R3 R4 R6
• The DR on a source network encapsulates

the multicast server’s traffic and forwards it
to the appropriate RP for distribution.
Multicast group
• A DR connected to a network with receivers members
originates the PIM Join messages that add the
network to the distribution tree.
Rev. 10.41 5 - 19
Bootstrap Router Election: 1

After all PIM neighbor relationships have been
BSR
established, each BSR Candidate originates Bootstrap R7
messages .1 .1 .1 Candidate
Bootstrap message for each interface.
Each PIM router forwards the Bootstrap messages
to its PIM neighbors, replacing the Layer 2 and 10.1.64.0/24 10.1.65.0/24 10.1.66.0/24
Layer 3 headers
headers. The message is transmitted
transmitted,
.2 .2
one hop at a time, throughout the domain. .2
BSR
R1 R2 R5
The BSR Candidate with the highest priority is .1 .1
Candidate
elected as the BSR of the domain. The active BSR
10.1.5.0/24
will be responsible for distributing messages that 10.1.12.0/24
associate multicast address ranges with .2
.2
Rendezvous Points (RP). R3 R4 R6
If the active BSR becomes unavailable, the BSR

Candidate with the next highest priority becomes
assumes its responsibilities.
bl
Bootstrap Router Election: 2

Bootstrap Message sent by Router R7 Over Interface 10.1.64.1
Ethernet header:
Dest: 01:00:5e:00:00:0d Source: <R7_MAC>
Type: IP (0x0800)
Bootstrap messages are sent to the All PIM
IP datagram header: Routers multicast group. Each PIM router
Protocol: PIM (0x67) (Decimal: 103) changes the packet’s Layer 2 and Layer 3
Source: 10.1.64.1 Destination: 224.0.0.13 addresses as it forwards the Bootstrap
message.
Version: 2
Type: Bootstrap (4)
PIM parameters:
t These
h values
l determine
d which
h h BSRS Candidate
C dd willll
Hash mask len: 30 become the active BSR. The original BSR
BSR priority: 10 advertisement remains unchanged as the
BSR: 10.1.66.1 Bootstrap message PIM is propagated throughout
the domain.
Rev. 10.41 5 - 20
Technet24.ir
Rendezvous Point Candidate

BSR for the
Each multicast group requires a Rendezvous Point domain
(RP) to serve as the root of the distribution tree. R7
.1 .1 .1
After the BSR has been elected, each candidate
originates RP-Candidate advertisements
addressed to the BSR. 10.1.64.0/24 10.1.65.0/24 10.1.66.0/24
To achieve fault tolerance, configure at least two .2 .2 .2 BSR Candidate

RP candidates with identical or overlapping
R1 R2 R5
address ranges. .1
In the example, two PIM-SM routers are

10.1.5.0/24
configured as RP Candidates for the entire
.2
multicast address range.
R3 R4 R6
Rendezvous Point Candidate: 2

RP Candidate Advertisement from Router R2
Ethernet header:
Dest: <R7_MAC> Source: <R2_MAC>
Type: IP (0x0800)
RP Candidates send their advertisements
IP datagram header: directly to the elected BSR, and not the PIM
Protocol: PIM (0x67) (Decimal: 103) multicast group.

Version: 2
Type: Candidate RP Advertisement (8)
PIM parameters: The PIM portion of the packet
Prefix count: 1 lists the multicast address ranges
y 255
Priority: associated with this RP.
Holdtime: 150
RP: 10.1.65.2
Group: 224.0.0.0/4
Rev. 10.41 5 - 21
Advertising RP-to-Group Mappings: 1

BSR for the
When the BSR has received RP Candidate domain
advertisements, its Bootstrap messages expand R7
to include the associations between RPs and .1 .1 .1
multicast group addresses. This association is

known as the “RP-Set.” 10.1.64.0/24 10.1.65.0/24 10.1.66.0/24
As the
A h BBootstrap messages move through
h h the
h .2
.2
domain, each PIM-SM router stores this .2
information in a table. RP Candidate

R1 .1
R2 RP for R5
BSR Candidate
.1 224.0.0.0/4
When a multicast receiver in network 10.1.4.0/24
10.1.6.0/24 joins a group by issuing an IGMP 10.1.5.0/24
Membership Report, the edge router (R6) uses .2
its table to identify the RP for that group. .2
R3 R4 R6
R6 sends a PIM Join message upstream to
define the path to the RP. The tree that has the
RP at its root is known
k as the
h “RP Tree.”
T ”
Advertising RP-to-Group Mappings: 2

Bootstrap Message Containing Mappings
Ethernet header:
Dest: 01:00:5e:00:00:0d Source: <R7_MAC>
Type: IP (0x0800) The BSR originates a copy of the Bootstrap
message for each of its interfaces that support
IP datagram
d t h
header:
d PIM neighbors.
i hb It is
i sentt tto th
the multicast
lti t address
dd
Protocol: PIM (0x67) (Decimal: 103) that includes all PIM routers.

Type: Bootstrap (4)
PIM parameters:
Hash mask len: 30
BSR priority: 10
BSR: 10.1.65.1
Group 0: 224224.0.0.0/4
0 0 0/4
RP count: 1
RP 0: 10.1.65.2 This message includes the RP-to-group
Priority: 192 mappings from all RP Candidate
Group 1: 224.0.0.0/4 Advertisements. Its contents are not
RP count: 1 limited to the active RP.
RP 0: 10.1.66.2
Priority: 255
Rev. 10.41 5 - 22
Technet24.ir
Sharing RP Responsibilities
Individual RPs can be configured to BSR for the

act as the root of a tree that supports Server 1: domain RP Candidate:
S: 10.1.5.17 R7 224.0.0.0/4
a subset of multicast addresses. This G: 239.64.11.37 .1 .1 .1
is often done to enable load sharing. Server 2:
S: 10.1.5.3
G: 239.192.12.42
In the example, R2 and R5 have 10.1.64.0/24 10.1.65.0/24 10.1.66.0/24
each been configured as .2

.2
Candidate RPs for only a portion of .2
the multicast address space. R7 is R1 R2 RP for R5 RP for

configured as an RP Candidate for .1
.1
239.192.0.0/10 239.64.0.0/10
the entire multicast address space. 10.1.4.0/24
10.1.5.0/24
As each multicast data transmission .2
begins, the Designated Router (DR) DR for Network .2
for the source network consults its 10.1.5.0/24 R3 R4 R6
PIM tables and learns the identity of
10.1.6.0/24 10.1.10.0/24
each RP
RP.
The DR encapsulates the traffic in an
Group Group
outer packet that specifies the unicast members: members:
IP address of the RP. The RP 239.192.12.42 239.64.11.37
decapsulates the packets and sends
them downstream.
The Shortest Path Tree
The placement of RPs must be BSR for the

carefully considered. Multicast traffic Server 1: domain RP Candidate:
between Server 1 and receivers in S: 10.1.5.17 R7 224.0.0.0/4
.1 .1 .1
the network 10.1.10.0/24 follows an Server 2:
G: 239.64.11.37
inefficient path because the traffic S: 10.1.5.3
must cross the RP for that group. G: 239.192.12.42
10.1.64.0/24
10 1 64 0/24 10 1 65 0/24
10.1.65.0/24 10.1.66.0/24
10 1 66 0/24
Placing RPs in a central location is .2 .2 .2

likely to produce a more efficient RP
Tree. However, appropriately R1
.1
R2 RP for R5 RP for
configured PIM-SM routers may shift .1 239.192.0.0/10 239.64.0.0/10
10.1.4.0/24
an established multicast traffic flow
10.1.5.0/24
from the RP Tree to the Shortest Path
.2
Tree (SPT). DR for Network .2
10.1.5.0/24 R3 R4 R6
The flow can shift to the SPT only after
the path through the RP has been 10 1 6 0/24
10.1.6.0/24 10 1 10 0/24
10.1.10.0/24
established.
Group Group
members: members:
239.192.12.42 239.64.11.37
Rev. 10.41 5 - 23
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
Technet24.ir
HP Switching and Routing Technologies Delivering Quality of Service
Module 6: Delivering Quality of Service

Objectives
This module will reveal some procedures and technologies that have been developed to enable
IP networks to support voice and video traffic. After completing this module, you will be able to:
• Compare and contrast the characteristics of and requirements for data traffic and real-time
traffic.
• Describe Layer 2 and Layer 3 prioritization standards and their appropriate implementations
in contemporary enterprise networks
• Describe the LLDP-MED standard and its relevance to QoS for VoIP and other applications
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

1- Gbps uplink
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
traffic is least likelyy to be discarded when congestion
g occurs.
… …
[20 gigabit clients @ 5% average utilization]
Rev. 10.41 6-1

TCP Traffic Characteristics

The response of senders and receivers to delayed and dropped packets depends on the transport
protocol they are using.
Data traffic is intolerant of dropped packets. At the start of a conversation, hosts using an application
that relies on TCP (rollover text: Transmission Control Protocol) set up an acknowledged, flow controlled
session.
Host1 Host2
Application Application
Transport
Among other items, the hosts negotiate a Transport
(TCP) window size (rollover text: limits the how (TCP)
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
Network (IP) length of time each host will wait for Network (IP)
Data Link acknowledgements from the other. Data Link
Physical Physical
TCP Provides Acknowledgment:1

TCP creates segments from each message it receives from the application. The TCP header contains a
segment number that represents the number of bytes offset from the start of the message. The receiver
uses this information to acknowledge packets to the sender and also to reassemble packets in the
correct order.
Host1 Host2
The transport layer creates

Transport
4 (TCP) sequentially numbered segments and Transport (TCP)
3 sends them to the Network layer.
2
1
The message may be

further segmented at
Network and Data Link
Network (IP) Layers as it is encapsulated Network (IP)
Data Link and transmitted. Data Link
Physical Physical
Rev. 10.41 6-2

Technet24.ir
TCP Provides Acknowledgment: 2

TCP creates segments from each message it receives from the application. The TCP header contains a
segment number that represents the number of bytes offset from the start of the message. The receiver
uses this information to acknowledge packets to the sender and also to reassemble packets in the
correct order.
Host1 Host2
Application If Host1 does not receive Host2 acknowledges receipt of Application
acknowledgement of packets 1 and 2 by including
packets 3 and 4 before its the highest received segment
Transport
4 (TCP) timer expires, it retransmits number in the TCP header of Transport (TCP)
3 them. packets it sends to Host1.
2
1
If the number of delayed or retransmitted packets is

outside a predefined tolerance level, the hosts negotiate
Network (IP) Network (IP)
a smaller window size, effectively backing down the
Data Link transmission speed. Data Link
Physical Physical
UDP Provides No Flow Control

User Datagram Protocol (UDP) is a simpler transport protocol. While it does add a header to identify
the originating application, it does not provide flow control or acknowledgement services.
Applications that transmit data traffic over UDP typically include their own acknowledgement
mechanism to force retransmission of lost packets. Without flow control, hosts have no way to detect
congestion and slow down their transmission. In this case, the packets retransmitted due to congestion
increase traffic volume,, leading
g to further congestion.
g
Host1 Host2
Transport (UDP) Transport (UDP)
Network (IP) Network (IP)

Data Link Data Link
Physical Physical
Rev. 10.41 6-3

Steps to Achieving QoS

A converged infrastructure must consider the special needs of time-sensitive traffic. You will learn more
about network design in other training. Generally speaking, however, designers follow some basic steps
to limit congestion.
1. Provision sufficient bandwidth: measure actual utilization or calculate based on well-known rules of
thumb:
• Average g bandwidth p per voice session: 3-100 Kbps
p
• Average bandwidth per video stream: 2-8 Mbps
2. Create broadcast domain boundaries that limit the scope of broadcast traffic
• Provide dedicated voice VLANs to prevent unnecessary data traffic
Even with the most careful planning, congestion is somewhat inevitable, requiring another step.
3. Enable time-sensitive traffic to be handled by network devices with higher priority than other traffic.
• The goal of prioritization is to limit jitter and delay.
• This module is focused on prioritization mechanisms.
3. Prioritize time-sensitive traffic ahead of

normal traffic
2. Control to eliminate unnecessary traffic
1. Provision sufficient bandwidth
Queuing Example for Undifferentiated Traffic

Queuing enables time-sensitive traffic to be forwarded ahead of normal traffic. It is not the only
mechanism, but it is the one we will look at first.
In this example, the switch accepts many types of traffic through edge ports and forwards them through its
uplink.
If all traffic types have the same priority, packets are forwarded in the order they arrive at the egress port.
A llong as there
As h is no congestion, this
h is satisfactory
f for
f allll types off traffic.
ff
When congestion occurs, packets arrive at the egress port more quickly than the uplink can transmit them.
Time-sensitive traffic is likely to arrive at its destination exhibiting unacceptable levels of jitter and delay.
Edge ports Uplink
UDP data
t ffi
traffic
Voice traffic
TCP data
traffic
Ingress ports Egress port
Rev. 10.41 6-4

Technet24.ir
Prioritized Queues Accept Differentiated Traffic

Time-sensitive traffic such as VoIP functions best in conditions of low jitter and delay. QoS-capable
switches ensure low levels of delay and jitter by transmitting time-sensitive traffic before data traffic,
which is less sensitive to delay.
Traffic that is identified as “high priority” is placed in a separate queue from other traffic.
For simplicity,
p y, we will use an example
p with four q
queues. Manyy QoS-capable
p switches support
pp eight
g
queues.
UDP data
4 ((highest
g es ppriority)
o y)
t ffi
traffic
3 (medium priority)
Voice traffic 2 (normal priority)
1 (lowest priority)
TCP data
traffic
Egress port
Ingress ports
queues
Strict Priority Queuing

If the switch is using “strict priority” queuing, all packets in higher priority queues will be serviced
(transmitted over the physical link) before any packets in lower priority queues.
Packets that arrive in higher priority queues will interrupt servicing of packets in lower priority queues.
This creates the opportunity for starving lower priority queues to the point that data traffic can suffer.
Edge ports Uplink
UDP data
traffic
ff 4
3
Voice traffic 2
1
TCP data
traffic
Ingress ports Egress port queues Egress port
Rev. 10.41 6-5

Weighted Fair Queuing

“Weighted fair queuing” is a method designed to ensure that no queue is completely starved from servicing. Each queue
is assigned a bandwidth percentage, and the total of all queue minimum bandwidth values equals 100%. The allocation
defines how much bandwidth each queue gets during a service cycle.
In the example, the highest priority queue (4) is allocated 45% of the total bandwidth. Higher priority queues are always
serviced before lower priority queues. When a number of bytes equal to this bandwidth percentage have been
forwarded,, the next highest
g p
priorityy q
queue is serviced.
Queue 3 is allocated a bandwidth percentage; however, it contains no waiting packets. Servicing moves on to the
normal priority queue (2), and the low priority queue (1). At the end of the cycle, the remaining capacity is allocated to
the highest priority queue that has packets waiting.
Edge ports Uplink
UDP data
traffic
ff 4 45%
3 15%
Voice traffic 35%
2
1 5%
TCP data
traffic
Ingress ports Egress port queues Egress port
Layer 2 Priority Marker

Devices requesting priority handling for their traffic include a marker indicating the priority level that
should be applied. Traffic may be marked within the 802.1Q tag in each packet’s Layer 2 header.
Layer 2 header IP datagram header Remainder of packet

(18 bytes) (20 bytes) (< 1500 bytes)
Dest. MAC Source MAC VLAN tag Type

(6 bytes) (6 bytes) (4 bytes) (2)
Canonical Format Indicator (1 bit)
IEEE 802.1Q tag
VLAN Protocol ID Priority VLAN ID (1-4094)
(16 bits) (3 bits) (12 bits)
000
001
010
011 8 possible values in
100 3-bit prioritization field
101
110
111
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

Technet24.ir
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 When mapped to When mapped to When mapped to

Traffic class
Binary Decimal 8 queues 4 queues 2 queues
111 7 (highest) 7 (highest) 8 (highest) 4 (high) 2
110 6 6 7
101 5 5 6 (medium) 3
100 4 4 5
011 3 3 4 (normal) 2 (normal) 1
010 0 (normal) 0 (normal) 3
001 2 2 2 (lowest) 1
000 1 (lowest) 1 (lowest) 1
Rev. 10.41 6-7

Switch Forwards Traffic With High Priority

Observe as we step through a simple prioritization scenario involving an HP Networking E-series switch, the 3500.
1. The phone marks voice traffic with priority level 6.

2. The switch interprets the priority value in the 802.1Q tag of inbound traffic.
3. The switch assigns the packet to traffic class 6 (Classify).
4. The switch places the packet in the outbound port queue associated with traffic class 6 (Schedule).
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
in decimal)

802.1Q tag
Retaining Priority When Routing

The next switch in the packet’s path is an HP networking E5406 switch.
Based on packet lookup, the switch has determined that the port leading Priority (binary) VLAN ID (decimal)
to the packet’s destination is in a different VLAN from the source port.
The switch interprets the priority value in the packet’s 802.1Q tag and
performs the following steps:
1. Classify:
y Assign
g the p packet to traffic class 6
8021Q tag
802.1Q
2. Mark: Record binary value 6 in the 802.1Q tag of the new header the
switch creates for the routed packet. Outbound port:
3. Schedule: Place the packet in the queue associated with traffic class 6. VLAN 132
Layer 3 switch
Inbound port:
VLAN 130
in decimal))

802.1Q tag
Layer 2 switch
Rev. 10.41 6-8

Technet24.ir
Forwarding Normal Priority Traffic

In this example, the switch accepts data traffic coming from an IP host connected to an untagged port. The switch
interprets this as normal traffic; however, because it will forward the packet over a tagged link, it performs all three steps:
1. Classify: assign packet to traffic class 0
2. Mark: record traffic class 0 in the 802.1Q tag the switch adds to the
packet.
3. Schedule: pplace the p
packet in the q queue associated with traffic class 0.
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
The inbound port is a

tagged member of
Priority (binary) VLAN ID (represented VLAN 24.
in decimal)

802.1Q tag
The uplink is a tagged

Layer 2 switch member of VLAN 24
This port is an untagged [MAC header] [IP header]

member of VLAN 24
(No 802.1Q tag) Host sending
untagged TCP traffic
Benefits of Marking Priority at Layer 3

Priority settings marked in the 802.1Q tag are typically retained by switches that forward a packet over
tagged links.
However, when a packet is forwarded over an untagged link, the tag is stripped, and the priority marker
is lost. This is true whether the packet in question is forwarded at Layer 2 or Layer 3.
The IP datagram header ttypically

picall remains intact when traffic is forwarded at both La
Layer
er 2 and La
Layer
er 3
3.
Layer 3 priority settings marked at the edge are likely to be retained from end to end.
A QoS-capable router is typically configured to interpret the contents of the 8-bit TOS field in one of two
ways.
Layer 2 header IP datagram header Remainder of packet

(18 bytes) (20 bytes) (variable <1500 bytes)
Version (4) HL (4 bits) Type of Service (8 bits) Total Length (16 bits)
Identifier (16 bits) Flags (3) Fragment Offset (13 bits)
Time to Live (8 bits) Protocol (8 bits) Header Checksum (16 bits)
Source Address (32 bits)
Destination Address (32 bits)
Rev. 10.41 6-9

IP Precedence ToS Definition

The original ToS definition is IP Precedence. It uses three most significant (high order) bits in the ToS field.
Positions 3-7 of the TOS field are unused in most implementations.
The decimal value of the entire TOS field is 160.
A packet decoder would display the hexadecimal value of the entire TOS field: A0.
DiffServ ToS Definition

Differentiated Services (DiffServ) is a more recent definition, using six bits in the ToS field.
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
Technet24.ir
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
Using VLANs to Isolate Voice Traffic

In most cases, a phone and PC share the same physical connection to an edge switch port. The phone is
connected directly to the jack, and the user’s PC is connected to a port on the phone.
The phone contains a two-port MAC relay that tags VoIP traffic with the ID of the voice VLAN, and sends
PC traffic untagged. Isolating voice and data traffic in separate VLANs is an accepted VoIP best
p
practice.
Assignment of phones to voice VLANs may be time-consuming for a large deployment. LLDP-MED is a
standard protocol which enables, among many other items, dynamic assignment of phone connections to
voice VLANs.
To wiring
closet
2-port
MAC
relay
Rev. 10.41 6 - 11
Basic LLDP Review: 1

LLDP is a simple, two-way protocol that enables standardized in 2005 as IEEE 802.1AB. Devices supporting LLDP send
periodic advertisements containing system and source port identification, software image versions, serial numbers, and
many other items.
• 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 Device Type Info
A1 Switch1 Switch xxxx Switch2
A1
MIB
Port Device Type Info
50 Switch2 Router xxxx
Switch1
50 Switch ID &
capabilities
Basic LLDP Review: 2

LLDP Message
Rev. 10.41 6 - 12
Technet24.ir
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

To learn more about HP networking, visit

www.hp.com/networking
© 2010 Hewlett-Packard Development Company, L.P. 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.

HP Switching and Routing Technologies: Web-Based Training Course Companion

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HP Switching and Routing Technologies: Web-Based Training Course Companion

Uploaded by

Copyright:

Available Formats

HP Switching and Routing Technologies

Web-based Training Course Companion

HP Switching and Routing Technologies

Converged Applications Drive Infrastructure Enhancements

IP Telephony Video conferencing and Video surveillance

Rev. 10.41 1-1

Convergence Requires High Availability 1

HP networking products can enhance resilience on many levels by supporting:

Instance 1 Primary default gateway Instance 1 Backup default gateway

Links that are active

Links that are active

Convergence Requires High Availability 2

Connections to other resources and client systems

Rev. 10.41 1-2

Redundant Components in Network Devices

• Redundant management module – failover to hot standby module

• Redundant, hot-swappable power supplies – providing N+1 power protection –

Real-time Traffic Requires Predictability

Senders of real-time traffic Receivers expect the packets to

Rev. 10.41 1-3

IP Telephony Traffic Requires Low Delay

IP Telephony Requires Intelligence at the Edge

Rev. 10.41 1-4

Rev. 10.41 1-5

Module 2: Providing Redundant Links and Gateways

The source and destination IP addresses do not

Router1 Host1 Host1 Server Payload

Host 1 All IP hosts require a gateway in their

Rev. 10.41 2-1

The host will need to reconfigure its default gateway and

The Virtual Router Redundancy Protocol (VRRP) may

Owner (Master) Non-owner (Backup)

VLAN 10 - Virtual Router ID: 1

Rev. 10.41 2-2

VRRP Virtual MAC Address

Owner (Master) Non-owner (Backup)

VLAN 10 - Virtual Router ID: 1

Gratuitous ARP Request

Address Resolution Protocol header: Virtual Router ID

• IP Address 10.1.10.1 = MAC Address 00:00:5e:00:01:01

Rev. 10.41 2-3

Master VLAN 10: 10.1.10.1/24 Backup VLAN 10: 10.1.10.2/24

VLAN 10 VRRP Advertisement

Rev. 10.41 2-4

VLAN 10: 10.1.10.1/24 (Owner) VLAN 10: 10.1.10.2/24 (Backup)

VLAN 10 - VRID: 1: 10.1.10.1

VLAN 20 : VRID 2: 10.1.20.1

VRRP Master Failover: 1

Rev. 10.41 2-5

VRRP Master Failover: 2

VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

Rev. 10.41 2-6

VRRP Advertisements and Spanning Tree

VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

Gateway Load Sharing in a Single Spanning Tree: 1

VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

Rev. 10.41 2-7

Gateway Load Sharing in a Single Spanning Tree: 2

VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

HostA Router2 HostB HostA Payload

Gateway Load Sharing in a Single Spanning Tree: 3

VLAN 10: 10.1.10.1/24 VLAN 10: 10.1.10.2/24

HostA Router2 HostB HostA Payload