Cis185 ROUTE 1 BasicNetworkRoutingConcepts

CIS 185 CCNP ROUTE
Chapter 1: Basic Network and Routing

Concepts
Rick Graziani
Cabrillo College
graziani@cabrillo.edu
Spring 2017
Ch. 1 Basic Network and Routing Concepts
 Differentiating Routing Protocols  Connecting Remote Locations
 Enterprise Network Architecture  Static Routing
 Routing Protocols  PPP Overview
 Understanding Network Technologies  Frame Relay Overview
 Traffic Types  Types of VPNs
 Network Types and Frame Relay  MPLS Overview
Challenges  Virtual Routing and Forwarding (VRF) and
 TCP/IP Cisco EVN
 IPv4 and IPv6 Headers  VPN Overview
 TCP MSS  Tunnels
 Path MTU Discovery  Characteristics of a Secure VPN
 TCP BDP  DMVPN and NHRP Concepts
 TCP Starvation  IPv6 Overview
 ICMP Redirect  GUA
 Asymmetric Routing  Link-local address
 ICMPv6 ND
 Implementing RIPng 2
Enterprise
Network
Infrastructure
A high-level overview of a
typical enterprise network, it
can be divided into two
major areas:
 Enterprise Campus
 Enterprise Edge
3
Enterprise Network
Infrastructure
 Enterprise Campus:
 Provides access to the network communications services and resources
to end users and devices.
 Usually scalable hierarchical model
 Access layer
 Distribution layer
 Core layer
4
Enterprise Network
Infrastructure
 Enterprise Edge:
 Provides:
 Access to the Internet
 Access to the same network services as users at the main site.
5
Role of Dynamic
Routing Protocols
Routing protocols provide:
 Network reachability between routers
 Dynamically adapt to network
changes
 Best practice that you use one IP (IGP) routing protocol throughout the
enterprise.
 OSPF or EIGRP
 Multiple routing protocols (IGP and BGP) are used when the organization is
multihomed to two or more ISPs for Internet connectivity.
6
 BGP with ISP
Choosing a Dynamic Routing Protocol
 Input (network) requirements
 Size of the network (scalability)
 Vendor interoperability
 Familiarity
 What’s currently being used
 Protocol characteristics:
 IGP or EGP
 Type of routing algorithm
 Speed of convergence
 Scalability
 Summarization 7
IGP versus EGP
 Interior Gateway Protocols
(IGP): These are used within
the organization, and they
exchange the routes within
an AS.
 RIP
 EIGRP
 OSPF
 IS-IS
 Exterior Gateway Protocols (EGP): Used to exchange routes
between different ASs.
 BGP is the only EGP that is used today.
8
Types of Routing Protocols
Exterior
Gateway
Interior Gateway Protocols Protocols
Distance Vector Link State Path Vector
Distance Vector Routing Link State Routing Path Vector
Protocols Protocols
IPv4 RIPv2 EIGRP OSPFv2 IS-IS BGP-4
RIPng EIGRP for OSPFv3 * IS-IS for BGP-4 for
IPv6 IPv6 IPv6 IPv6 or
MP-BGP
* OSPFv3 supports routing both IPv4 and IPv6.
9
Distance Vector Routing Protocols
 What does a street sign like this tell you?
 How far (distance)
 Which way (direction)
 Distance vector
 Routes are advertised as vectors of
distance and direction.
 Distance is defined in terms of a metric
 Such as hop count
 Direction is simply the:
 Next-hop router or
 Exit interface
 Typically use the Bellman-Ford algorithm for
10
the best-path (shortest) route determination
Link-State Protocols
 Link-state routing protocol can
create a “complete view,” or
topology, of the network.
 Link-state protocols are associated
with Shortest Path First (SPF)
calculations. OR
 A link-state router uses the link-
state information to:
 Create a topology map
 Select the best path to all
destination networks in the
topology.
 Each router makes the decision!
Link State routing protocols is like having a complete map of the network topology 11
Path vector protocols
 Path vector protocols:

 Exchanges information about:
 The existence of destination networks
 The path on how to reach the destination
 Path information is used to determine the best paths and to prevent
routing loops.
12
Convergence
 Convergence is when a
network has complete and
accurate information
about the entire network
 Convergence time is
how fast network devices
can reach the state of
convergence after a
topology change.
 Convergence time
affected by:
 Routing protocol
timers
 Route summarization
13
Route Protocol Scalability
 Scalability describes the ability of a routing
protocol to support further network growth.
 Scalability factors include:
 Number of routes
 Number of adjacent neighbors
 Number of routers in the network
 Addressing scheme
 Network design
 Frequency of changes
 Available resources (CPU and memory)
 Hierarchical addressing, structured address
assignment, and route summarization improve
the overall scalability regardless of routing protocol
type.
14
 Connecting Remote Locations
 Differentiating Routing Protocols
 Static Routing
 Enterprise Network Architecture
 PPP Overview
 Routing Protocols
 Frame Relay Overview
 Understanding Network Technologies
 Types of VPNs
 Traffic Types
 MPLS Overview
 Network Types and Frame Relay
 Virtual Routing and Forwarding (VRF) and
Challenges
Cisco EVN
 TCP/IP
 VPN Overview
 IPv4 and IPv6 Headers
 Tunnels
 TCP MSS
 Characteristics of a Secure VPN
 Path MTU Discovery
 DMVPN and NHRP Concepts
 TCP BDP
 IPv6 Overview
 TCP Starvation
 GUA
 ICMP Redirect
 Link-local address
 Asymmetric Routing
 ICMPv6 ND
IP Source and Destination IPv4
Addresses
• IP Source – Always a unicast
• IP Destination – Unicast, multicast, anycast
(or broadcast for IPv4).
IPv6
Traffic Types
 Destination IP address: A device can send traffic to one
recipient, to selected recipients, or to all devices within a
subnet at the same time.
 Routing protocols use different traffic types to control how
routing information is exchanged.
 Unicast: Unicast addresses are used in a one-to-one context.
 Multicast: Multicast addresses identify a group of interfaces.
 Traffic that is sent to a multicast address is sent to multiple
destinations at the same time.
 Anycast: It is assigned to an interface on more than one node.
 When a packet is sent to an anycast address, it is routed
to the nearest interface that has this address.
 Broadcast: IPv4 broadcast addresses are used when sending
traffic to all devices in the subnet.
17
Well-known IPv4 and IPv6 multicast addresses used by
routers
 Notice the relationship between IPv4 and IPv6 multicast addresses. 18

Network Types
 Three general network types:
 Point-to-point network: A network that connects a single
pair of routers. (Serial)
 Broadcast network: A network that can connect many
routers along with the capability to address a single
message to all of the attached routers. (Ethernet)
 NBMA network: A network that has single access to
multiple networks but no broadcast capability.
 Sender needs to create an individual copy of the same
packet for each recipient.
 NBMA networks introduce several challenges.
 (Frame Relay and ATM)
 Not all Layer 2 network topologies support all traffic types.
19
Frame Relay Point-to-Point
Physical interface: Same Network
 One connection to
provider
 Alternative: Separate
leased lines for each
point-to-point
connection Sub-interface: Sub-interface for each separate network
20
 Point-to-point subinterfaces are logical interfaces:
 Emulates a leased line network
 Provide a routing equivalent to point-to-point physical interfaces
 As with physical point-to-point interfaces, each interface requires its own
subnet.
 Frame Relay point-to point is applicable to hub and spoke topologies.
21
Nonbroadcast Multiple-Access Networks
 NBMA networks introduce several challenges.

 Distance vector (RIP and EIGRP): Split horizon
 Link-state (OSPF): DR (Designated Router)
22
Split horizon:
 Prevents a routing update that is received on an interface from being
forwarded out of the same interface.
 Hub router will not forward routing update learned from one spoke router to
other spoke routers.
 Solution: Disable split horizon or subinterfaces
23
DR
Designated Router:
 OSPF over NBMA networks works in a nonbroadcast network mode by default
 The hub router will not forward broadcasts/multicasts received by one
spoke to other spokes.
 Default, OSPF treats an NBMA network like Ethernet.
 Requires a DR to exchange routing information between all routers on a
segment.
 Solution: Configure the hub router to act as a DR because it is the only router
that has PVCs with all other routers. 24
Replicated Broadcasts
Broadcast replication:
 The router must replicate broadcast (and multicast) packets, such as
routing update broadcasts, on each PVC to the remote routers.
 Consume bandwidth and cause significant latency variations in user traffic.
25
Challenges
 VPN Overview
 TCP/IP
 Tunnels
 TCP MSS
 IPv6 Overview
 TCP BDP
 GUA
 TCP Starvation
 ICMP Redirect
 ICMPv6 ND
 Implementing RIPng
 Virtual Routing and Forwarding (VRF)
26
and Cisco EVN
From: 2.1: Comparing the IPv4 and IPv6 Headers
IPv6 Fundamentals LiveLessons: A

Straightforward Approach to Understanding IPv6
• By Rick Graziani
• ISBN-10: 1-58720-457-6
• The following slides are from my IPv6 LiveLessons video series.

• Check out my IPv6 Resource Page for more information including
PowerPoint presentations, videos and links
• http://www.cabrillo.edu/~rgraziani/ipv6.html
Similar fields
Let’s Begin with looking at IP Headers
• Understanding IPv6 begins with the IPv6 IPv4
header.
• IPv6 takes advantage of 64-bit CPUs.
• Several differences between IPv4 and IPv6
headers.
• Simpler IPv6 64-bit memory word

header.
IPv6
• Fixed 40 byte
IPv6 header.
• Lets look at the
differences…
IPv6 Version
• IPv4 Version contains 4. IPv4
• IPv6 Version contains 6.
• Version 5?
• Internet Stream Protocol (ST2)
IPv6
IPv4 Internet Header Length
IPv4
• IPv4 Internet Header Length (IHL) 1
• Length of IPv4 header in 32-bit 2
words including any Options or
3
Padding.
4
• IPv6
• IHL for IPv6 is not needed. 5
• IPv6 header is fixed at 40 bytes. ?
IPv6
8 bytes
8 bytes
40 bytes = 8 bytes
8 bytes
8 bytes
IPv6 Traffic Class
• IPv4 Type of Service IPv4
• IPv6 Traffic Class
• Not mandated by any IPv6 RFCs.
• Same functionality as IPv4.
• Uses same Differentiated Services
technique (RFC 2474) as IPv4.
IPv6
7 6 5 4 3 2 1 0
IP Precedence Unsused
DiffServ Code Point (DSCP) IP ECN

IPv6 Flow Label
• New field in IPv6 – not part of IPv4. IPv4
• Flow label is used to identify the packets in a common stream or flow.
• Traffic from source to destination share a common flow label.
• RFC 6437 IPv6 Flow Label Specification
11001011000101100
10110010111000111
IPv6
IPv4 Header Data (Payload)
IPv6 Payload Length
• IPv4 Total Length – Number of bytes of IPv4
the IPv4 header (options) + data.
• IPv6 Payload Length – Number of bytes
of the payload.
• Does not include the main IPv6
header.
• Includes extension headers + data
IPv6
Payload
IPv6 Extension
IPv6 Header Header (Optional) Data
IPv4 Fragmentation
• IPv4 fields used for fragmentation and IPv4
reassembly.
• Intermediate devices such as IPv6
routers do not perform fragmentation.
• Any fragmentation needed will be
handled by the source using an
extension header.
IPv6
IPv4 Fragmentation MTU of outgoing link It is my job to
smaller than packet size reassemble the packet
– fragment IPv4 packet. fragments.
PCA Link with PCB

R1 R2 smaller MTU R3
Source Destination
1 2 3
IPv4
IPv4
IPv4 Packet Packet IPv4 Packet
Packet
IPv4
IPv4
Packet
Packet
IPv4
IPv4
Packet
Packet
IPv6 No Fragmentation MTU of outgoing link smaller
Packet received.
than packet size. Drop packet.
No reassembly
I will use MTU of the Send ICMPv6 Packet Too Big
required.
interface. message, use MTU 1350.
MTU = 1500 MTU = 1500 MTU = 1350 MTU = 1500

PCA PCB
R1 R2 Link with R3
smaller MTU
Source Destination
1
IPv6 Packet – MTU 1500
2
ICMPv6 Packet Too Big
Use MTU 1350
3
IPv6 Packet
MTU 1350
IPv6 Next Header
• IPv4 Protocol IPv4
• IPv6 Next Header
• For both protocols, the field indicates the
type of header following the IP header.
• Common values:
• 6 = TCP
IPv6
• 17 = UDP
• 58 = ICMPv6
• 88 = EIGRP
• 89 = OSPF IPv6 Next Data
Header Header (Protocol: TCP, UDP, ICMPv6, etc.)
IPv6 Hop Limit
• IPv4 TTL (Time to Live) IPv4
• IPv6 Hop Limit
• Renamed to more accurately reflect process.
• Set by source, every router in path
decrements hop limit by 1.
• When 0, drop
packet. IPv6
IPv6 Source and Destination Addresses
• IPv6 Source and Destination addresses IPv4
have the same basic functionality as IPv4.
• IPv4 – 32-bit addresses.
• IPv6 – 128-bit addresses.
• Some significant changes in IPv6.
IPv6
IPv4 Header Checksum
• IPv4 Header Checksum
IPv4
• Not used in IPv6.
• Upper-layer protocols generally have a
checksum (UDP and TCP).
• So, in IPv4 the UDP checksum is optional.
• Because it’s
not in IPv6, the IPv6
UDP checksum
is now
mandatory.
IPv4 Options and Padding
• IPv4 Options and Padding IPv4
• Not used in IPv6.
• Variable length, optional.
• IPv4 Options are handled using
extension headers in IPv6.
• Padding makes
sure IPv4 options
fall on a 32-bit
IPv6
boundary.
• IPv6 header is
fixed at 40 bytes.
40 bytes =
IPv6 Extension Header
• Next Header identifies:
• The protocol carried in the data
portion of the packet.
• The presence of an extension header.
• Extension headers are optional and follow the main IPv6 header.
• Provide flexibility and features to the main IPv6 header for future enhancements
without having to redesign the entire protocol.
• Allows the main IPv6 header to have a fixed size for more efficient processing.
IPv6 Main Next Extension Next Data

Header Header Header Header (Protocol: TCP, UDP, ICMPv6, etc.)
IPv6 Extension Header
Next Header Value Extension Header Extension Header Description
(Decimal) Name
0 Hop-by-Hop Options Used to carry optional information, which must be examined by every
router along the path of the packet.
43 Routing Allows the source of the packet to specify the path to the destination.
44 Fragment Used to fragment IPv6 packets.
50 Encapsulating Used to provide authentication, integrity, and encryption.

Security Payload
(ESP)
51 Authentication Header Used to provide authentication and integrity.
(AH)
60 Destination Options Used to carry optional information that only needs to be examined by a
packet’s destination node(s).
Next Hop-by-Hop Next Next

IPv6 Main Header Header AH Extension Header TCP
Extension
Header Data
Header 0 Header 51 6 Header
MSS and
Avoiding
Fragmentation
 TCP MSS (Maximum Segment Size) defines the largest amount of data that the
receiving device is able to accept in a single TCP segment.
 To avoid fragmentation of an IPv4 packet, the selection of the TCP MSS is the
minimum buffer size and MTU of outgoing interface minus 40 bytes.
 The 40 bytes takes into account the 20 byte IPv4 header and the 20 bytes TCP
header.
 A TCP segment over IPv4 sent out an Ethernet interface will have a TCP MSS
of 1460, which is 1500 bytes for the Ethernet MTU, minus 20 bytes for the IPv4
header, and minus 20 bytes for the TCP header. 44
Path MTU Discovery (PMTUD)
 Used to determine the lowest MTU along a path

1. IPv4 host uses full TCP MSS determined by the outgoing interface
2. Sets the TCP DF (Don’t Fragment) bit
3. If an IPv4 router along the path needs to fragment the packet because of a
lower MTU link on the egress interface:
a. Drop the packet due to the DF bit being set
b. Sends an ICMP Destination Unreachable message back to the originator of
the packet with egress interface MTU.
 The PMTUD operations for IPv6 are similar to that of PMTUD for IPv4. 45
Bandwidth Delay Product (BDP)
100 Mbps pipe
More data is required to

keep this pipe full of data 1 Gbps pipe
 Long Fat Network (or long fat pipe) LFN ("elephan (t) )” - Network paths with
high bandwidth and long round-trip delays.
 TCP can experience bottlenecks on LFNs (less than optimal use these paths)
 Because of the increased bandwidth and the distance, we need to send more
data to keep the pipe full.
 Increased bandwidth – We can send more data
 Increased distance – Takes longer to send the data and get TCP Acks 46
 BDP is used to optimize the TCP window size to fully utilize the link.
 BDP = Bandwidth (bps) * RTT in seconds
 The TCP window size (amount of data that can be sent before requiring an
ACK) should then use the BDP.
 The result is the maximum amount of data that can be transmitted on the link at
any given time.
 http://www.speedguide.net/bdp.php
47
48
TCP Starvation
UDP
Not always possible to separate TCP and
UDP-based flows, important to be aware of
Wasted this behavior when mixing applications using
bandwidt both UDP and TCP.
h
TCP
Combination of TCP and UDP flows during a period of congestion:

 TCP backs off on bandwidth (window size) known as slow start
 Then begins to increase windows size
 All devices begin to have the same experience and synchronization
happens.
 UDP has no flow control mechanisms continues
 UDP has the potential of using up the available bandwidth given up by TCP.
 This is known as TCP starvation/UDP dominance. 49
WRED
 Global or TCP synchronization – TCP slow start, when all of our connections
do this together, router’s ingress queue fills and drops new packets
 Solution - RED or WRED, drops some packet sooner (minimum and max
thresholds)
 Only a few TCP flows have to go into TCP slow start and not everyone
 “Good of the many outweigh the good of the few or one”
 Different thresholds for different priorities so higher priority packets have a less
likely chance of being dropped – a lower priority packet will be dropped first.
50
ICMP Redirect Network X
R1 R2
Destination:
Network
PCB X Host
IPv6
Network A PCA PCB IPv6
Network B
• Similar functionality as ICMPv4.

• Like IPv4, a router informs an originating host of the IP address of a router that
is on the local link and is closer to the destination.
• Unlike IPv4, a router informs an originating host that the destination host (on a
different prefix/network) is on the same link as itself.
Asymmetric Routing
 Asymmetric routing - A packet traverses from a source to a destination in one

path and takes a different path when it returns to the source.
 This is commonly seen in Layer-3 routed networks.
 Not necessarily a bad thing – Internet and BGP.
 1 – 3: DSW1 (Active HSRP routers) is
3 4
default gateway for PC1
 4 - 5: CSW1 load balances sending
return traffic to DSW2 (not a bad thing)
 6: DSW2 ARP table (4 hour default) has 6
entry for PC1 10.1.1.100… 2 5 ARP Cache
10.1.1.100 >
 7: But there is no entry in its MAC table MacAdd
(times out 5 min)
7
 Both access layer switches are on same
Mac Add Table
VLAN (not a best practice). 1 8 FLOOD No entry
 8: So, DSW2 floods “frames” out all ports
on that VLAN (unicast flooding)
 Because DSW2 never sees traffic
sourced from PC1 (10.1.1.100) it never
updates is MAC address table and
unicast flooding always occurs. 53
Solutions:
1. Change ARP timer (4 hours IOS) to be
less than MAC Address Table (5 minutes)
timer
 DSW2 would need send ARP
request for 10.1.1.100 ARP Cache
 PC1 would send ARP Reply X
10.1.1.100 >
MacAdd
 ARP Reply in Ethernet frame, so
DSW2 can now add PC1’s MAC
Mac Add Table
address to its MAC address table No entry
PC1 MAC = Port
 DSW2 will now send packet for
10.1.1.100 only out the one port
2. Do not span VLAN across multiple
access layer switches
54
 Connecting Remote Locations
 Differentiating Routing Protocols
 Static Routing
 Enterprise Network Architecture
 PPP Overview
 Routing Protocols
 Frame Relay Overview
 Understanding Network Technologies
 Types of VPNs
 Traffic Types
 MPLS Overview
 Network Types and Frame Relay
 Virtual Routing and Forwarding (VRF) and
Challenges
Cisco EVN
 TCP/IP
 VPN Overview
 Tunnels
 TCP MSS
 TCP BDP
 IPv6 Overview
 TCP Starvation
 GUA
 ICMP Redirect
 ICMPv6 ND
Principles of Static Routing
2001:DB8:CAFE:1::/64 2001:DB8:CAFE:2::/64 2001:DB8:FEED:1::/64
S0/0/0 2001:DB8:FEED:2::/64
G0/0 S0/0/0 2001:DB8:FEED:3::/64
:2
:1 R1 :1 R2 2001:DB8:FEED:4::/64
2001:DB8:FEED:5::/64
Static Route
R2(config)# ipv6 route 2001:db8:cafe:1::/64 2001:db8:cafe:2::1
A static route can be used in the following circumstances:

 Undesirable to have dynamic routing updates forwarded across slow bandwidth links.
 Administrator needs total control over the routes used by the router.
 Floating static route: Backup to a dynamically recognized route is necessary.
 Necessary to reach a network accessible by only one path (a stub network).
 Router connects to a single ISP and needs to have only a default route pointing
toward the ISP router, rather than learning many routes from the ISP.
 Router is underpowered and does not have the CPU or memory resources necessary
to handle a dynamic routing protocol.
56
Using VPNs
 What kind of connection?
 Traditionally leased lines or frame relay.
 Takes time to provision
 VPNs
 Easy to provision
 Used over different technologies –
DSL, cable, DS/gig circuits
 Can provide security
59
Types of VPNs
 Types of VPNs used for remote access:

 MPLS-based VPN
 Tunnel-based VPN (sometimes referred to as IPsec VPNs, but
doesn’t have to be IPsec)
 Hybrid VPN (combination)
 Focus on VPN tunnels 60
MPLS overview
 MPLS (Multi-protocol label switching) is a

switching mechanism.
 A 32 bit header (label) is inserted by the
provider (PE) router.
 Packets are switched through the MPLS
network.
 The label is removed by the PE at the other
end of the MPLS network.
 To the customer, it looks like a Layer 2 or
Layer 3 connection.
61
Cisco EVN (Easy Virtual Network)
 Pure IP alternative to MPLS is VRFs

 Virtual Routing and Forwarding (VRF) is a technology that
allows the device to have multiple but separate instances of routing
tables exist and work simultaneously.
 VRF-Lite makes it easier
 EVN (Easy Virtual Network) is easier and more scalable
 More in Chapter 8 including a cool simple lab! 62
 IPv4 and IPv6 Headers  VPN Overview (Read: Hidden slides)
 ICMPv6 ND
 ICMPv6 ND
IPv6 Address Types
IPv6 Addresses
Unicast Multicast Anycast
Assigned Solicited-Node
FF00::/8 FF02::1:FF00:0000/104
Global Unique Embedded

Link-Local Loopback Unspecified
Unicast Local IPv4
2000::/3 FE80::/10 ::1/128 ::/128 FC00::/7 ::/80
3FFF::/3 FEBF::/10 FDFF::/7
IPv6 does not have a “broadcast” address.

Global Unicast Address Range
Global Routing Prefix Subnet ID Interface ID
001 Range: 2000::/3 0010 0000 0000 0000 ::

to 3FFF::/3 0011 1111 1111 1111 ::
• Global Unicast Address (GUA)

• 2000::/3 (2000::/3 to 3FFF::/3)
• 1/8th of IPv6 address space
IANA’s allocation of IPv6

address space in 1/8th sections
Parts of a Global Unicast Address
IPv4 Unicast Address /?
Network portion Subnet portion Host portion
32 bits
IPv6 Global Unicast Address

/48 /64
16-bit Fixed
Global Routing Prefix Interface ID
Subnet ID
128 bits
• 64-bit Interface ID = 18 quintillion (18,446,744,073,709,551,616) devices/subnet
• 16-bit Subnet ID = 65,536 subnets
/64 Global Unicast Address and the 3-1-4 Rule
/48 /64
16 bits 16 bits 16 bits 16 bits 16 bits 16 bits 16 bits 16 bits
Global Routing Prefix Subnet ID Interface ID

3 1 4
2001 : 0DB8 : CAFE : 0001 : 0000 : 0000 : 0000 : 0100
3 + 1 = 4 (/64) : 4
2001:0DB8:CAFE:0001:0000:0000:0000:0100/64
2001:0DB8:CAFE:0001::100/64
2001:DB8:CAFE:1::/64
Static GUA :100 A G0/0
:1
2001:DB8:CAFE:3::/64
:1
Configuration :100
:1
G0/0
R1 S0/0/0
B
2001:DB8:CAFE:2::/64
I love the 3-1-4
rule and
R1(config)#interface gigabitethernet 0/1
subnetting IPv6!
R1(config-if)#ipv6 address 2001:db8:cafe:2::1/64
R1(config-if)#no shutdown
R1(config-if)#exit
R1(config)#interface serial 0/0/0
R1(config-if)#ipv6 address 2001:db8:cafe:3::1/64
R1(config-if)#no shutdown
R1(config-if)#exit
Unlike IPv4, IPv6 does not associate the all-zeroes and all-ones Interface-IDs
(host portion) to subnet/broadcast – valid IPv6 device addresses.
IPv6 Address Allocation
Global Routing Prefix I am getting a /64 at home
/23 /32 /48 /56 /64
Subnet
Sub Interface ID
ID
*RIR
*ISP Prefix
*Site Prefix
Possible Home Site Prefix
Subnet Prefix
* This is a minimum allocation. The prefix-length may be less if it can be justified.

PI versus PA Address Space
/32 /48
Subnet
Global Routing Prefix ID Interface ID
Provider Independent (PI) Address Space

• Address space that is assigned by the RIR.
• Remains assigned to the customer regardless of provider
• No prefix renumbering needed if change providers
Provider Aggregatable (PA) Address Space
• Address space that is typically assigned by an ISP to a customer.
• Change provider, must get new address space
• Customer must do prefix renumbering (Helpful IETF RFCs)
Link-Local Unicast Range
First 10 bits
1111 1110 10xx xxxx Remaining 54 bits 64-bit Interface ID
Range: FE80::/10 1111 1110 1000 0000 ::

to FEBF::/10 1111 1110 1011 1111 ::
Link-local Unicast
• Link – Network segment

• Link-local means, local to that
link or network.
Link-Local Unicast Address
Link-Local Communications
• Used to communicate with other devices on the link.

• Are NOT routable off the link (network).
• Only have to be unique on the link.
• Not included in the IPv6 routing table.
• An IPv6 device must have at least a link-local address.
Link-Local Unicast Address
First 10 bits
1111 1110 10xx xxxx Remaining 54 bits 64-bit Interface ID
FE80::Interface ID
Link-local addresses are created
• Automatically :
• FE80 (usually) – First 10 bits
• Interface ID
• EUI-64 (Cisco routers)
• Random 64 bits (many host operating systems)
• Static (manual) configuration
G0/0
Automatic Link-Local Address S0/0/0
R1
using EUI-64 G0/1
R1# show interface gigabitethernet 0/0

GigabitEthernet0/0 is up, line protocol is up
Hardware is CN Gigabit Ethernet, address is fc99.4775.c3e0 (bia
fc99.4775.c3e0)
<Output Omitted>
Link-local address: FE80:: 64-bit Interface ID

A 64-bit Interface ID is created with EUI-64 using:
• 48-bt MAC address
• Inserting 16 bits: FF-FE
• Flipping the U/L (Universal/Local) bit
Modified EUI-64 Format (Extended Unique Identifier–64)
OUI (24 bits) Device Identifier (24 bits)
FC 99 47 75 C3 E0
Insert FF-FE
FC 99 47 FF FE 75 C3 E0
FC
1111 1100
1110 99 47 FF FE 75 C3 E0
U/L bit flipped
FE 99 47 FF FE 75 C3 E0
G0/0
Verifying the Router’s S0/0/0
R1
Link-Local Address G0/1
R1# show interface gigabitethernet 0/0
GigabitEthernet0/0 is up, line protocol is up
Hardware is CN Gigabit Ethernet, address is fc99.4775.c3e0 (bia
Link-local
fc99.4775.c3e0) addresses
<Output Omitted> only have to
Wait! Two be unique
R1#show ipv6 interface brief Link-locals on the link.
GigabitEthernet0/0 [up/up] are the
FE80::FE99:47FF:FE75:C3E0
2001:DB8:CAFE:1::1
EUI-64 same!
GigabitEthernet0/1 [up/up]
FE80::FE99:47FF:FE75:C3E1 FF:FE = EUI-64 (most likely)
2001:DB8:CAFE:2::1
Serial0/0/0 [up/up]
FE80::FE99:47FF:FE75:C3E0
Serial interfaces will use a MAC
2001:DB8:CAFE:3::1 address of an Ethernet interface.
R1#
G0/0
Static Link-Local Addresses FE80::1 S0/0/0
Static addresses are more easily remembered G0/1 R1 FE80::1
and recognizable. FE80::1
R1(config)#interface gigabitethernet 0/0
R1(config-if)#ipv6 address fe80::1 ?
link-local Use link-local address
R1(config-if)#ipv6 address fe80::1 link-local Link-Local

R1(config-if)#exit Addresses only
R1(config)#interface gigabitethernet 0/1 have to be unique
R1(config-if)#ipv6 address fe80::1 link-local on the link!
R1(config-if)#exit
R1(config)#interface serial 0/0/0
R1(config-if)#ipv6 address fe80::1 link-local
R1(config-if)#
Unicast Addresses
• Loopback Address
• ::1/128
• Used by a node to send an IPv6 packet to itself, typically when testing the
TCP/IP stack.
• Same functionality as IPv4 loopback 127.0.0.1
• Not routable.
• Unspecified Address
• :: (all-0s)
• Indicates the absence or anonymity of an IPv6 address (RA source address)
Unicast Addresses
Note: Site local addresses (FEC0::/10)
has ben deprecated.
• Unique Local Address

• FC00::/7 (FC00::7 to FDFF::/7)
• Similar to RFC 1918 IPv4 addresses but …
• Not meant to be translated to a global unicast (for security purposes)
• IETF does not support the concept of translating a “private IPv6” address
to a “public” IPv6 address... but there are exceptions
• Should not be routable in the global Internet.
• To be used in a more limited area such as within a site or devices inaccessible
from the global Internet.
• FC00::/7 – 1111 110x (x = local flag bit)
• FC00::/8 (x = 0) - /48 prefix assigned using RFC 4193 algorithm (dormant)
• FD00::/8 (x = 1) - /48 prefix locally locally assigned.
ICMPv6 and ICMPv6-ND
Internet Control Message Protocol for IPv6
• ICMPv6 is defined in RFC 4443.
• ICMPv6 Neighbor Discovery is described in
RFC 4861.
• Much more robust than ICMP for IPv4.
• Contains new functionality and
improvements.
• More than just “messaging” but “how IPv6
conducts business”.
Next
All ICMPv6 IPv6 Main Header ICMPv6
Data
messages Header 58 Header
ICMPv6 Neighbor Discover Protocol
ICMPv6 Neighbor Discovery defines 5 different packet types:
• Router Solicitation Message
• Router Advertisement Message Router-Device
Messaging
Used with dynamic address allocation
• Neighbor Solicitation Message

• Neighbor Advertisement Message Device-Device
Used with address resolution (IPv4 ARP) Messaging
• Redirect Message
Similar to ICMPv4 redirect message
Router-to-Device messaging
 ICMPv6 ND
Comparing RIPv2 and RIPng
99
Configuring RIP (IPv4)
192.168.3.0/24
192.168.1.0/24 .1 G0/0 192.168.5.0/24

.1 DCE DCE .1
S0/0/0 S0/0/0 S0/0/1 S0/0/1
G0/0 R1 R2 R3 G0/0
.1 .2 .2 .1
192.168.2.0/30 192.168.4.0/30
R1(config)# router rip

R1(config-router)# network 192.168.1.0
R1(config-router)# network 192.168.2.0
R1(config-router)#
100
Configuring RIPng
101
Similar configuration made on R1’s
Eth0/3, Lo0 and Lo1
R2(config)# ipv6 router rip CCNP_RIP

% IPv6 routing not enabled
R2(config)# ipv6 unicast-routing
R2(config)# ipv6 router rip CCNP_RIP ! Created automatically if
enabled on the interface first
R2(config)# interface ethernet 0/1
R2(config-if)# ipv6 rip CCNP_RIP enable
R2(config-if)# exit
R2(config)# interface loopback 0
R2(config-if)# ipv6 rip CCNP_RIP enable 102
R2# show ipv6 protocols
IPv6 Routing Protocol is "connected"
IPv6 Routing Protocol is "ND"
IPv6 Routing Protocol is "rip CCNP_RIP"
Interfaces:
Loopback0
Ethernet0/1
Redistribution:
None
103
2nd hop 1st hop
R2# show ipv6 route

IPv6 Routing Table - default - 7 entries
<output omitted>
R 2001:DB8:A01:100::/64 [120/2]
via FE80::A8BB:CCFF:FE00:130, Ethernet0/1
R 2001:DB8:A01:A00::/64 [120/2]
C 2001:DB8:A01:1400::/64 [0/0]
via Ethernet0/1, directly connected  RIPng routers add one hop to
the metric when it receives the
L 2001:DB8:A01:1400::2/128 [0/0] RIPng update.
via Ethernet0/1, receive  In effect, including itself as one
C 2001:DB8:A01:1E00::/64 [0/0] hop.
via Loopback0, directly connected  RIP and RIPv2 routers do not
L 2001:DB8:A01:1E00::1/128 [0/0] include themselves in the
via Loopback0, receive number of hops to the
L FF00::/8 [0/0] destination network.
via Null0, receive 104
Connected Routes
R2# show ipv6 route
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
<Output omitted>
R 2001:DB8:A01:100::/64 [120/2]
R 2001:DB8:A01:A00::/64 [120/2] [Administrative Distance/Metric]
C 2001:DB8:A01:1400::/64 [0/0]
via Ethernet0/1, directly connected
L 2001:DB8:A01:1400::2/128 [0/0]
via Ethernet0/1, receive
C 2001:DB8:A01:1E00::/64 [0/0]
via Loopback0, directly connected
L 2001:DB8:A01:1E00::1/128 [0/0]
• via Loopback0, receive
ICMPv6
L FF00::/8 [0/0]
via Null0, receive
Local Routes
R2# show ipv6 route
IPv6 Routing Table - default - 6 entries • Local routes are /128 routes
Codes: C - Connected, L - Local, S - Static, U (host routes)
- Per-user for the
Static router’s
route
<Output omitted>
IPv6 unicast addresses.
• Allows the router to more
R 2001:DB8:A01:100::/64 [120/2]
efficiently process packets
R 2001:DB8:A01:A00::/64 [120/2] directed to the router itself
via FE80::A8BB:CCFF:FE00:130, Ethernet0/1 rather than for packet
C 2001:DB8:A01:1400::/64 [0/0]
via Ethernet0/1, directly connected forwarding.
L 2001:DB8:A01:1400::2/128 [0/0]
C 2001:DB8:A01:1E00::/64 [0/0]
L 2001:DB8:A01:1E00::1/128 [0/0]
ICMPv6
L FF00::/8 [0/0]
via Null0, receive
FF00::/8 to Null0
R1# show ipv6 route
• By default multicast packets
Codes: C - Connected, L - Local, S - Static, U - Per-user
(FF00::/8) are notStatic route
forwarded.
<Output omitted>
• Any ‘more specific’ multicast
packets (such as FF05::1:3 All-
R 2001:DB8:A01:100::/64 [120/2]
DHCPv6 servers) would take
R 2001:DB8:A01:A00::/64 [120/2] precedence.
• ipv6 multicast-routing
C 2001:DB8:A01:1400::/64 [0/0]
via Ethernet0/1, directly connected would need to be configured
L 2001:DB8:A01:1400::2/128 [0/0] • Link-local multicast (FF02) are
C 2001:DB8:A01:1E00::/64 [0/0] never forwarded off the link.
L 2001:DB8:A01:1E00::1/128 [0/0]
ICMPv6
L FF00::/8 [0/0]
via Null0, receive
Propagating a Default Route
 originate keyword originates
the default route (::/0) in
addition to all other routes in
the updates sent on this
interface.
 only keyword originates the
default route (::/0) but
suppresses all other routes in
the updates sent on this
interface.
R1(config-if)# ipv6 rip name default-information originate | only
108
originate option
R1(config)# ipv6 route ::/0 2001:DB8:FEED:1::1

R1(config)# interface Ethernet 0/3
R1(config-if)# ipv6 rip CCNP_RIP default-information originate
R2# show ipv6 route rip
<output omitted>
R ::/0 [120/2]
R 2001:DB8:A01:100::/64 [120/2]
R 2001:DB8:A01:A00::/64 [120/2]
via FE80::A8BB:CCFF:FE00:130, Ethernet0/1 109
only option
R1(config)# ipv6 route ::/0 2001:DB8:FEED:1::1

R1(config)# interface Ethernet 0/3
R1(config-if)# ipv6 rip CCNP_RIP default-information only
R2# show ipv6 route rip

<output omitted>
R ::/0 [120/2]
110
Investigating the RIPng Process
R2# show ipv6 rip
RIP process "CCNP_RIP", port 521, multicast-group FF02::9, pid
138
Administrative distance is 120. Maximum paths is 16
Updates every 30 seconds, expire after 180
Holddown lasts 0 seconds, garbage collect after 120
Split horizon is on; poison reverse is off
Default routes are not generated
Periodic updates 308, trigger updates 1
Full Advertisement 0, Delayed Events 0
Interfaces:
Loopback0
Ethernet0/1  The show ipv6 rip command shows information
Redistribution: about all RIPng routing processes on the router.
None  There can be mulitple RIPng processes on a
R2# single router
111
Investigating the RIPng Database
R2# show ipv6 rip database
RIP process "CCNP_RIP", local RIB
2001:DB8:A01:100::/64, metric 2, installed
Ethernet0/1/FE80::A8BB:CCFF:FE00:7430, expires in 155 secs
2001:DB8:A01:A00::/64, metric 2, installed
2001:DB8:A01:1400::/64, metric 2
R2#
 The RIP routing protocol uses an internal database to store routes received
from RIP neighbors.
 This database is also used to generate outbound RIP updates.
112
R2# show ipv6 rip database
RIP process "CCNP_RIP", local RIB
2001:DB8:A01:100::/64, metric 2, installed
<output omitted>
 The RIP process (there can be mulitple RIPng processes on a single router).
 The route prefix.
 The route metric, destination network is 2 hops away, counting itself as a hop.
 Installed or expired:
 "installed" means the route is in the routing table as a RIPng route. Entries may not be
installed such a prefix that is directly connected.
 If a network becomes unavailable, the route will become "expired" after the dead timer
expires (180 seconds).
 Exit interface and next-hop link-local address
 Expires in, in which if the countdown timer reaches 0, the route is removed from the routing table
and marked expired. This timer, the dead timer, is by default three times the hello timer—180
seconds. 113
R2# show ipv6 rip next-hops
RIP process "CCNP_RIP", Next Hops
FE80::A8BB:CCFF:FE00:7430/Ethernet0/1 [3 paths]
R2#
 The show ipv6 rip next-hops lists RIPng processes and under each
process all next-hop addresses.
 Includes a next-hop address and the associated exit interface where the
route was learned.
 Displays information about the next hop addresses for the specified RIP
IPv6 process.
 If no RIP process name is specified, the next-hop addresses for all RIP IPv6
processes are displayed.
114
CIS 185 CCNP ROUTE
Chapter 1: Basic Network and Routing
Concepts
Rick Graziani
Cabrillo College
graziani@cabrillo.edu

Cis185 ROUTE 1 BasicNetworkRoutingConcepts

Uploaded by

Document Information

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

Cis185 ROUTE 1 BasicNetworkRoutingConcepts

Uploaded by

Copyright:

Available Formats

CIS 185 CCNP ROUTE

Chapter 1: Basic Network and Routing

 Path vector protocols:

 Notice the relationship between IPv4 and IPv6 multicast addresses. 18

 NBMA networks introduce several challenges.

IPv6 Fundamentals LiveLessons: A

• The following slides are from my IPv6 LiveLessons video series.

• Simpler IPv6 64-bit memory word

DiffServ Code Point (DSCP) IP ECN

PCA Link with PCB

MTU = 1500 MTU = 1500 MTU = 1350 MTU = 1500

IPv6 Main Next Extension Next Data

44 Fragment Used to fragment IPv6 packets.

50 Encapsulating Used to provide authentication, integrity, and encryption.

Next Hop-by-Hop Next Next

 Used to determine the lowest MTU along a path

More data is required to

Combination of TCP and UDP flows during a period of congestion:

• Similar functionality as ICMPv4.

 Asymmetric routing - A packet traverses from a source to a destination in one

A static route can be used in the following circumstances:

 Types of VPNs used for remote access:

 MPLS (Multi-protocol label switching) is a

 Pure IP alternative to MPLS is VRFs

Unicast Multicast Anycast

Global Unique Embedded

IPv6 does not have a “broadcast” address.

001 Range: 2000::/3 0010 0000 0000 0000 ::

• Global Unicast Address (GUA)

IANA’s allocation of IPv6

Network portion Subnet portion Host portion

IPv6 Global Unicast Address

Global Routing Prefix Subnet ID Interface ID

2001 : 0DB8 : CAFE : 0001 : 0000 : 0000 : 0000 : 0100

* This is a minimum allocation. The prefix-length may be less if it can be justified.

Provider Independent (PI) Address Space

Range: FE80::/10 1111 1110 1000 0000 ::

• Link – Network segment

• Used to communicate with other devices on the link.

R1# show interface gigabitethernet 0/0

Link-local address: FE80:: 64-bit Interface ID

R1(config-if)#ipv6 address fe80::1 link-local Link-Local

• Unique Local Address

• Neighbor Solicitation Message

192.168.1.0/24 .1 G0/0 192.168.5.0/24

R1(config)# router rip

R2(config)# ipv6 router rip CCNP_RIP

R2# show ipv6 route

R1(config-if)# ipv6 rip name default-information originate | only

R1(config)# ipv6 route ::/0 2001:DB8:FEED:1::1

R1(config)# ipv6 route ::/0 2001:DB8:FEED:1::1

R2# show ipv6 route rip

You might also like