Sei sulla pagina 1di 201

IP Orientation Training For NSN India Delivery Leadership Team

Mitrabh Shukla Head RSO IP Stream

For internal use only


1
Nokia Siemens Networks

Agenda

Reference Architecture Context Setting

3G Network
LTE Network
Core PaCo Node
Peering

Module 1: IP Basics

IP Networking Fundamentals
Reference Models - TCP/IP and OSI
IP Addressing and Subnetting
Fundamentals of LAN

Module 2: Switching & Routing Introduction

LAN Switching
Spanning Tree Protocol
WAN Protocols
Gateway Redundancy Protocol
Routing Overview (OSPF & BGP)

Module 3: MPLS Introduction

MPLS
MPLS
MPLS
MPLS
MPLS

(Multi Protocol Label Switching) Overview


VPNs
QoS
Traffic Engineering
High Availability

Module 4: Advance IP Features


For internal use only
2
Nokia Siemens Networks

IPv6 Introduction
IP Evolution Roadmap

Reference Point 1: Reference Model (OSI &


TCP/IP)

For internal use only


3
Nokia Siemens Networks

Layers with TCP/IP and OSI Model


Compare OSI and TCP/IP model
A framework (guideline) for network
implementation and troubleshooting
Divides complex functions into simpler
components
Importance of reference model:
Vendor interoperability standardization.
Better understanding of data transfer

Reference model types :


OSI (Open System Interconnection ).reference
model
TCP/IP (DOD Model).commercial model

For internal use only


4
Nokia Siemens Networks

Physical Layer Protocols & Services

For internal use only


5
Nokia Siemens Networks

Transport Layer

TCP
UDP

For internal use only


6
Nokia Siemens Networks

OSI Transport Layer


Objectives
1.

2.
3.
4.

5.
6.
7.

Roles of the Transport Layer


1. segmentation of data
2. error detection
3. Multiplexing of upper layer application using port numbers
The TCP protocol Communicating with reliability (TCP Header)
TCP Connection Establishment (TCP Three-Way Handshake)
Managing TCP Sessions
1. reliability (sequencing and acknowledgements)
2. In order TCP Segment Reassembly
3. error correction -(TCP Retransmission)
4. flow control ( window size)
TCP Session Termination ( 4 Way handshake)
The UDP protocol Communicating with Low overhead (UDP Header)
TCP VS. UDP

For internal use only


7
Nokia Siemens Networks

What is the protocol which implement transport layer ?

UDP Header

TCP Header

or

TCP Header=20 bytes


UDP Header=8 bytes
UDP is lower overhead

For internal use only


8
Nokia Siemens Networks

Application
Header + data

TCP Connection Establishment


When two hosts communicate using TCP, a connection
is established before data can be exchanged.
After the communication is completed, the sessions are
closed and the connection is terminated.
To establish the connection, the hosts perform a threeway handshake.
Control bits in the TCP header indicate the progress
and status of the connection.

For internal use only


9
Nokia Siemens Networks

TCP Connection Establishment and Termination


Within the TCP segment header, there are six 1-bit fields
that contain control information used to manage the
TCP processes. Those fields are:
1. URG - Urgent pointer field significant
2. ACK - Acknowledgement field significant
3. PSH - Push function
4. RST - Reset the connection
5. SYN - Synchronize sequence numbers
6. FIN - No more data from sender

For internal use only


10
Nokia Siemens Networks

TCP Three-Way Handshake

For internal use only


11
Nokia Siemens Networks

TCP Three-Way Handshake


Step 1:
A TCP client begins the three-way handshake by sending a segment with the
SYN (control flag set, indicating an initial value in the sequence number field in the
header.
The sequence number is the Initial Sequence Number (ISN), is randomly chosen
and is used to begin tracking the flow of data from the client to the server for this
session.
Step 2:
Server sends a segment back to the client with:
ACK flag set indicating that the Acknowledgment number is significant.
The value of the acknowledgment number field is equal to the client initial
sequence number plus 1.
SYN flag is set with its own random ISN for the Sequence number
Step 3:
TCP client responds with a segment containing an ACK that is the response to the
TCP SYN sent by the server.
The value in the acknowledgment number field contains one more than the initial
sequence number received from the server.

For internal use only


12
Nokia Siemens Networks

TCP Session Termination


Session termination

For internal use only


13
Nokia Siemens Networks

Whats meant by window


size

Flow Control and Reliability


To govern the flow of data between devices, TCP uses a peer-to-peer flow control
mechanism.
The receiving host's TCP layer reports a window size to the sending host's TCP
layer.
This window size specifies the number of bytes, starting with the acknowledgment
number, that the receiving host's TCP layer is currently prepared to receive.
Window size is included in every TCP segment sent from client or server starting
with three-way handshake.
TCP is a full duplex service, client and server specify their own window sizes.
For internal use only
14
Nokia Siemens Networks

Segmentation and reassembly.


Describe the role of segments in the transport layer and
the two principle ways segments can be marked for
reassembly.

For internal use only


15
Nokia Siemens Networks

TCP In order Reassembly


Describe how TCP sequence numbers are used to
reconstruct the data stream with segments placed in the
correct order

For internal use only


16
Nokia Siemens Networks

UDP out of order Datagram Reassembly


Describe in detail the process specified by the UDP
protocol to reassemble PDUs at the destination device

For internal use only


17
Nokia Siemens Networks

Summary TCP vs. UDP


TCP provides:
Reliable delivery
Error checking
Flow control
Congestion control
Ordered delivery
(Connection establishment)
Applications:
HTTP
FTP
Telnet
MSN messenger

 UDP provides:
Unreliable delivery
No error checking
No flow control
No congestion control
No ordered delivery
(No connection establishment)
Applications
DNS (usually)
SMTP
RTP (Real-Time Protocol)
VoIP

For internal use only


18
Nokia Siemens Networks

Network Layer Protocols

For internal use only


19
Nokia Siemens Networks

Network Layer Protocols

For internal use only


20
Nokia Siemens Networks

Network Layer Protocols and Internet Protocol (IP)

For internal use only


21
Nokia Siemens Networks

Network Layer Protocols and Internet Protocol (IP)

For internal use only


22
Nokia Siemens Networks

Other IPv4 fields

Version - Contains the IP version number (4)


Header Length (IHL) - Specifies the size of the packet header.
Packet Length - This field gives the entire packet size, including
header and data, in bytes.
Identification - This field is primarily used for uniquely identifying
fragments of an original IP packet
Header Checksum - The checksum field is used for error checking
the packet header.
Options - There is provision for additional fields in the IPv4 header to
provide other services but these are rarely used.
For internal use only
23
Nokia Siemens Networks

Grouping Devices into Networks and Hierarchical


Addressing

For internal use only


24
Nokia Siemens Networks

Binary & Decimal Numbering System

For internal use only


25
Nokia Siemens Networks

Classify and Define IPv4 Addresses

For internal use only


26
Nokia Siemens Networks

IP address Classes

For internal use only


27
Nokia Siemens Networks

Subnet mask

For internal use only


28
Nokia Siemens Networks

Private IP Addresses
Private IP addresses are another solution to the problem of the impending
exhaustion of public IP addresses.As mentioned, public networks require hosts to
have unique IP addresses.
However, private networks that are not connected to the Internet may use any host
addresses, as long as each host within the private network is unique.

For internal use only


29
Nokia Siemens Networks

Subnetting

For internal use only


30
Nokia Siemens Networks

Subnetting

For internal use only


31
Nokia Siemens Networks

Subnetting

For internal use only


32
Nokia Siemens Networks

Subnetting

For internal use only


33
Nokia Siemens Networks

Data Link Layer Accessing the Media

For internal use only


34
Nokia Siemens Networks

Media access control addressing and framing data

For internal use only


35
Nokia Siemens Networks

The role of the trailer

For internal use only


36
Nokia Siemens Networks

Physical and Data Link Features of Ethernet


Media Access Control (MAC)

For internal use only


37
Nokia Siemens Networks

Layer 2 Header
The Frame Encapsulating the Packet

For internal use only


38
Nokia Siemens Networks

FCS

For internal use only


39
Nokia Siemens Networks

MAC Address

For internal use only


40
Nokia Siemens Networks

MAC Address Vs IP Address

For internal use only


41
Nokia Siemens Networks

MAC Address Vs IP Address

For internal use only


42
Nokia Siemens Networks

MAC Address Vs IP Address

For internal use only


43
Nokia Siemens Networks

MAC Address Vs IP Address

For internal use only


44
Nokia Siemens Networks

Address Resolution Protocol (ARP) operation

For internal use only


45
Nokia Siemens Networks

Address Resolution Protocol (ARP).


Mapping IP to MAC Addresses

For internal use only


46
Nokia Siemens Networks

Address Resolution Protocol (ARP).


ARP Destinations Outside the Local Network

For internal use only


47
Nokia Siemens Networks

Address Resolution Protocol (ARP).

It happens when a host ask for


MAC address which isnt in
the same LAN for any
reason.
Router will act as a proxy
gateway for that host.

For internal use only


48
Nokia Siemens Networks

Explain the Address Resolution Protocol (ARP)


process.
ARP Removing Address Mappings

For internal use only


49
Nokia Siemens Networks

Explain the Address Resolution Protocol (ARP)


process.
ARP Broadcasts - Issues

For internal use only


50
Nokia Siemens Networks

Hierarchical Network Design

For internal use only


51
Nokia Siemens Networks

Hierarchical Network Design

For internal use only


52
Nokia Siemens Networks

Hierarchical Network Design

For internal use only


53
Nokia Siemens Networks

Uncontrolled collision & broadcast domains

For internal use only


54
Nokia Siemens Networks

Reference Point 2: Layer 2 Switching


Concepts

For internal use only


55
Nokia Siemens Networks

Three Switch Functions at Layer-2

For internal use only


56
Nokia Siemens Networks

Empty MAC table

For internal use only


57
Nokia Siemens Networks

How Switches Learn Hosts Locations

For internal use only


58
Nokia Siemens Networks

Virtual Local Area Network (VLAN)

For internal use only


59
Nokia Siemens Networks

Virtual Local Area Network (VLAN)

For internal use only


60
Nokia Siemens Networks

Virtual Local Area Network (VLAN)

For internal use only


61
Nokia Siemens Networks

Using spanning tree protocol (STP)

For internal use only


62
Nokia Siemens Networks

Using spanning tree protocol (STP)

For internal use only


63
Nokia Siemens Networks

Using spanning tree protocol (STP)

For internal use only


64
Nokia Siemens Networks

Using spanning tree protocol (STP)

For internal use only


65
Nokia Siemens Networks

The STP Root Bridge


Reference point
One root per VLAN
Maintains topology
Propagates timers

For internal use only


66
Nokia Siemens Networks

Using spanning tree protocol (STP)

For internal use only


67
Nokia Siemens Networks

How STP select the root bridge?


Firstly : choose the root bridge
The lowest Bridge ID (BID)
 The lowest bridge priority
 The lowest MAC address

For internal use only


68
Nokia Siemens Networks

Spanning tree path cost

For internal use only


69
Nokia Siemens Networks

Spanning tree path cost

For internal use only


70
Nokia Siemens Networks

Reference Point 3: Gateway Redundancy


Protocols

For internal use only


71
Nokia Siemens Networks

HSRP (Hot Standby Routing Protocol)


HSRP, a Cisco proprietary
protocol, supplies a method of
providing nonstop path
redundancy for IP by sharing
protocol and MAC addresses
between redundant gateways.
The protocol consists of a:
virtual MAC address
IP address
These are shared between two
routers, and a process that
monitors both LAN and serial
interfaces via a multicast
protocol.

For internal use only


72
Nokia Siemens Networks

One standby router


One virtual router
The backup router in case the The virtual router is not
active router fails for the
an actual router.
subnet.
Rather, it is a concept of
In that case, the standby
the entire HSRP group
router becomes the active
acting as one virtual
router and starts
router as far as hosts on
forwarding traffic destined
the subnet are
to the virtual IP address.
concerned.
For internal use only
73
Nokia Siemens Networks

One active router


The active router
forwards traffic
destined to the virtual
IP address.

ARP Table
172.16.10.110 = 0000.0c07.ac01

172.16.10.169
0010.0b79.5800

My default
gateway is
172.16.10.110

172.16.10.110
0000.0c07.ac01

172.16.10.82
0010.f6b3.d000

The host connected to the switch sends the packet destined for the
virtual router, but in reality the active router does the packet
forwarding.
Note: Additional HSRP member routers Other routers are neither active
nor standby, but they are configured to participate in the same HSRP
group.
They monitor the current active and standby routers and transition into
one of those roles if the current router fails for the subnet.
For internal use only
74

Nokia Siemens Networks

ARP Table

My default
gateway is
172.16.10.110

172.16.10.110 = 0000.0c07.ac01

172.16.10.110
0000.0c07.ac01
172.16.10.169
0010.0b79.5800

172.16.10.82
0010.f6b3.d000
HSRP Hellos: Active

The active router assumes and maintains its active role through the transmission of
hello messages (default 3 seconds).
The hello interval time defines the interval between successive HSRP hello
messages sent by active and standby routers.
The router with the highest standby priority in the group becomes the active
router.
The default priority for an HSRP router is 100; however, this option is configurable
on a per-standby-group basis.
When the preempt option is not configured, the first router to initialize HSRP
becomes the active router
For internal use only
75
Nokia Siemens Networks

ARP Table

My default
gateway is
172.16.10.110

172.16.10.110 = 0000.0c07.ac01

172.16.10.110
0000.0c07.ac01
172.16.10.169
0010.0b79.5800

172.16.10.82
0010.f6b3.d000
HSRP Hellos: Standby

The second router in the HSRP group to initialize or second highest priority is
elected as the standby router.
The function of the standby router is to monitor the operational status of the
HSRP group and to quickly assume packet-forwarding responsibility if the active
router becomes inoperable.
The standby router also transmits hello messages to inform all other routers in the
group of its standby router role and status.

For internal use only


76
Nokia Siemens Networks

ARP Table

My default
gateway is
172.16.10.110

172.16.10.110 = 0000.0c07.ac01

I receive and
forward
packet sent
to the virtual
router.

172.16.10.110
0000.0c07.ac01
172.16.10.169
0010.0b79.5800

172.16.10.82
0010.f6b3.d000

The virtual router presents a consistent available router (default gateway) to the
hosts.
The virtual router is assigned its own IP address and virtual MAC address;
however, the active router acting as the virtual router actually forwards the
packets.
Additional HSRP member routers: These routers in listen state monitor the hello
messages but do not respond.
Do forward any packets addressed to the routers' IP addresses.
Do not forward packets destined for the virtual router because they are not the
active router.
For internal use only
77
Nokia Siemens Networks

ARP Table

My default
gateway is
172.16.10.110

172.16.10.110 = 0000.0c07.ac01
I dont see Hellos
from Active (10
secs), so I will
receive and forward
packet sent to the
virtual router.

New Active
Router

172.16.10.110
0000.0c07.ac01

172.16.10.169
0010.0b79.5800

172.16.10.82
0010.f6b3.d000
HSRP Hellos

HSRP Hellos: Active

When the active router fails, the other HSRP routers stop receiving hello
messages and the standby router assumes the role of the active router.
This occurs when the holdtime expires (default 10 seconds).
Because the new active router assumes both the IP address and virtual MAC
address of the virtual router, the end stations see no disruption in service.
The end-user stations continue to send packets to the virtual router's virtual MAC
address and IP address where the new active router delivers the packets to the
destination.
For internal use only
78
Nokia Siemens Networks

ARP Table
172.16.10.110 = 0000.0c07.ac01

172.16.10.169
0010.0b79.5800

My default
gateway is
172.16.10.110

172.16.10.110
0000.0c07.ac01

172.16.10.82
0010.f6b3.d000

If both the active and standby routers fail:


all routers in the HSRP group contend for the active and standby router
roles.
When the active router only fails:
the standby takes over.
If there are other routers participating in the group, those routers then
contend to be the new standby router.
The following sections discuss HSRP mechanics in more detail.
For internal use only
79

Nokia Siemens Networks

HSRP States
Initial state All routers begin in the initial state. This state is entered via a
configuration change or when an interface is initiated.
Learn state The router has not determined the virtual IP address, and has
not yet seen a hello message from the active router. In this state, the router
is still waiting to hear from the active router.
Listen state The router knows the virtual IP address, but is neither the
active router nor the standby router. All other routers participating in the
HSRP group besides the active or standby routers reside in this state.
Speak state HSRP routers in the speak state send periodic hello messages
and actively participate in the election of the active or standby router. The
router remains in the speak state unless it becomes an active or standby
router.
Standby state In the standby state, the HSRP router is a candidate to become
the next active router and sends periodic hello messages. There must be at
least one standby router in the HSRP group.
Active state In the active state, the router is currently forwarding packets that
are sent to the virtual MAC and IP address of the HSRP group. The active
router also sends periodic hello messages.
Not all HSRP routers transition through all states. For example, a router that is not
the standby or active router does not enter the standby or active states.
For internal use only
80
Nokia Siemens Networks

VRRP
Like HSRP, VRRP is a default gateway redundancy method.
VRRP enables a group of routers to form a single virtual
router.
The VRRP standard (RFC 2338) solves the static default
gateway configuration problem.
VRRP is similar in functionality to HSRP, and hence the LAN
hosts can be configured with the virtual router as their default
gateway.
The virtual router, representing a group of routers, is known as
a VRRP group.
Cisco switches and routers support VRRP on Ethernet, Fast
Ethernet, and Gigabit Ethernet interfaces, and on MPLS
VPNs and VLANs.
For internal use only
81
Nokia Siemens Networks

VRRP
The virtual router
can use a physical
IP address or a
virtual IP address.

Routers A, B, and C, are VRRP-enabled routers.


Routers A, B, and C form a virtual router, with 10.0.0.1 as the virtual IP address.
IP address of the virtual router is the same as that configured for the Ethernet interface of
Router A (10.0.0.1).
Because the virtual router uses the IP address of the physical Ethernet interface of router
A, router A assumes the role of the master virtual router and is known as the IP address
owner.
As the master virtual router, router A controls the IP address of the virtual router and is
responsible for forwarding packets sent to this IP address.
Hosts 1 through 3 are configured with the default gateway IP address of 10.0.0.1.
Routers B and C function as backup virtual routers.
If the master virtual router fails, the router configured with the higher priority will become
the master virtual router and provide uninterrupted service for the LAN hosts.
For internal use only
82
Nokia Siemens Networks
When
Router A recovers, it becomes the master virtual router again.

Reference Point 4: Layer 3: Routing


Concepts

For internal use only


83
Nokia Siemens Networks

What is Routing?
Routing Means : Selecting the Best Path
How could you select the Best Path ?
Statically
Dynamically

For internal use only


84
Nokia Siemens Networks

Routing Table Structure


Routing Table is stored in ram and contains information
about:

 Directly connected networks - this occurs when a

device is connected to another router interface


 Remotely connected networks - this is a network that
is not directly connected to a particular router
 Detailed information about the networks include source
of information, network address & subnet mask, and Ip
address of next-hop router
Show ip route command is used to view a routing table

For internal use only


85
Nokia Siemens Networks

Routing Table Structure


Adding a connected network to the routing table
-Router interfaces
 Each router interface is a member of a different network
 Activated using the no shutdown command
 In order for static and dynamic routes to exist in routing table you
must have directly connected networks

For internal use only


86
Nokia Siemens Networks

Routing Table Structure


Connected and Static routes

For internal use only


87
Nokia Siemens Networks

Routing Table Structure


Maintaining routing tables
-Dynamic routing protocols are used to share routing information with other
router & to maintain and up date their own routing table.

IP routing protocols. Example of routing protocols include:


-RIP
-IGRP
-EIGRP
-OSPF
-IS-IS
-BGP

For internal use only


88
Nokia Siemens Networks

Routing Table Structure


Routing Table Principles
-3 principles regarding routing tables:
 Every router makes its decisions alone, based on the information

it has in its routing table.


 Different routing table may contain different information
 A routing table can tell how to get to a destination but not how to
get back

For internal use only


89
Nokia Siemens Networks

Routing Table Structure


Effects of the 3 Routing Table Principles
-Packets are forwarded through the network from one router to
another, on a hop by hop basis.
-Packets can take path X to a destination but return via path Y
(Asymmetric routing).

For internal use only


90
Nokia Siemens Networks

Router Paths and Packet Switching


A Metric is a numerical value used by routing protocols help determine
the best path to a destination
The smaller the metric value the better the path
2 types of metrics used by routing protocols are:

-Hop count - this is the number of routers a packet must


travel through to get to its destination
-Bandwidth - this is the speed of a link also known as the
data capacity of a link

For internal use only


91
Nokia Siemens Networks

Router Paths and Packet Switching


Equal cost metric is a condition where a router has multiple paths to
the same destination that all have the same metric
To solve this dilemma, a router will use Equal Cost Load Balancing.
This means the router sends packets over the multiple exit
interfaces listed in the routing table.

For internal use only


92
Nokia Siemens Networks

Router Paths and Packet Switching


Path determination is a process used by a router to pick the best
path to a destination
One of 3 path determinations results from searching for the best path

Directly connected network


Remote network
No route determined

For internal use only


93
Nokia Siemens Networks

Router Paths and Packet Switching


Switching Function of Router is the process used by a
router to switch a packet from an incoming interface to an
outgoing interface on the same router.
-A packet received by a router will do the following:
 Strips off layer 2 headers.

 Examines destination IP address located in Layer 3 header


to find best route to destination.
 Re-encapsulates layer 3 packet into layer 2 frame.
 Forwards frame out exit interface.

For internal use only


94
Nokia Siemens Networks

Router Paths and Packet Switching


As a packet travels from one networking device to another
- The Source and Destination IP addresses NEVER
change
- The Source & Destination MAC addresses CHANGE
as packet is forwarded from one router to the next.
- TTL field decrement by one until a value of zero is
reached at which point router discards packet (prevents
packets from endlessly traversing the network)

For internal use only


95
Nokia Siemens Networks

Router Paths and Packet Switching


Path determination and switching function details. PC1
Wants to send something to PC 2 here is part of what
happens
Step 1 - PC1 encapsulates packet into a frame. Frame
contains R1s destination MAC address

For internal use only


96
Nokia Siemens Networks

Router Paths and Packet Switching


Step 2 - R1 receives Ethernet frame.






R1 sees that destination MAC address matches its own MAC.


R1 then strips off Ethernet frame.
R1 Examines destination IP.
R1 consults routing table looking for destination IP.
After finding destination IP in routing table, R1 now looks up next
hop IP address.
 R1 re-encapsulates IP packet with a new Ethernet frame.
 R1 forwards Ethernet packet out Fa0/1 interface.

For internal use only


97
Nokia Siemens Networks

Router Paths and Packet Switching

For internal use only


98
Nokia Siemens Networks

Router Paths and Packet Switching


Path determination and switching function details. PC1 Wants to send
something to PC 2 here is part of what happens

Step 3 - Packet arrives at R2









R2 receives Ethernet frame


R2 sees that destination MAC address matches its own MAC
R2 then strips off Ethernet frame
R2 Examines destination IP
R2 consults routing table looking for destination IP
After finding destination IP in routing table, R2 now looks up next
hop IP address
 R2 re-encapsulates IP packet with a new data link frame
 R2 forwards Ethernet packet out S0/0 interface

For internal use only


99
Nokia Siemens Networks

Router Paths and Packet Switching


Path determination and switching function details. PC1 Wants to send
something to PC 2 here is part of what happens

Step 4 - Packet arrives at R3








R3 receives PPP frame


R3 then strips off PPP frame
R3 Examines destination IP
R3 consults routing table looking for destination IP
After finding destination IP in routing table, R3 is directly
connected to destination via its fast Ethernet interface
 R3 re-encapsulates IP packet with a new Ethernet frame
 R3 forwards Ethernet packet out Fa0/0 interface

Step 5 - IP packet arrives at PC2. Frame is


decapsulated & processed by upper layer protocols.

For internal use only


100
Nokia Siemens Networks

Dynamic Routing Protocols


Function(s) of Dynamic Routing Protocols:
-Dynamically share information between routers.
-Automatically update routing table when topology changes.
-Determine best path to a destination.

For internal use only


101
Nokia Siemens Networks

Dynamic Routing Protocols


The purpose of a dynamic routing protocol is to:
-Discover remote networks
-Maintaining up-to-date routing information
-Choosing the best path to destination networks
-Ability to find a new best path if the current path is no
longer available

For internal use only


102
Nokia Siemens Networks

Dynamic Routing Protocols

For internal use only


103
Nokia Siemens Networks

Dynamic Routing Protocols


Components of a routing protocol
Algorithm
In the case of a routing protocol algorithms are used for facilitating
routing information and best path determination

Routing protocol messages


These are messages for discovering neighbors and exchange of
routing information

For internal use only


104
Nokia Siemens Networks

Dynamic Routing Protocols


Advantages of static routing
-It can backup multiple interfaces/networks on a router
-Easy to configure
-No extra resources are needed
-More secure
Disadvantages of static routing
-Network changes require manual reconfiguration
-Does not scale well in large topologies

For internal use only


105
Nokia Siemens Networks

Classifying Routing Protocols


Dynamic routing protocols are grouped according to
characteristics. Examples include:

Autonomous System is a group of routers under the control of a


single authority.

For internal use only


106
Nokia Siemens Networks

Classifying Routing Protocols


Types of routing protocols:
- Interior Gateway Protocols (IGP)
- Exterior Gateway Protocols (EGP)

For internal use only


107
Nokia Siemens Networks

Why Is It Called a Link State Protocol?


specific link characteristics and state information

For internal use only


108
Nokia Siemens Networks

Link State Protocol Operation


Zs Link State
Qs Link State
Z

X
Xs Link State

A
B
C

Q
Z
X

2
13
13

Topology Information Is
Kept in a Database
Separate from the Routing
Table

Uses costs to calculate path


Typically displays faster convergence than distance vector routing protocols
Typically more scalable due to hierarchical nature
For internal use only
109
Nokia Siemens Networks

OSPF Functions and Definitions


The high-level function of OSPF is
Discover neighbors and form adjacencies
Flood Link State Database (LSDB) information
Compute the shortest path
Install routes in route forwarding table
This section expands on these functions
Some definitions are needed first
(See text on the page with this slide)

For internal use only


110
Nokia Siemens Networks

Discovering Adjacent Neighbors


Discover neighbors with Hello packets
Form Adjacencies with appropriate neighbors
Exchange Link State Database (LSDB) information
using Link State Advertisements (LSA)
RID A

RID B
Hello, Im B
Hello, Im A
Lets exchange information
OK
I know about these links
I know about these links

For internal use only


111
Nokia Siemens Networks

Adjacency States
Sample Log showing adjacency process
P1R1(config-router)#log-adjacency-changes detail
6d04h: %OSPF-5-ADJCHG: Process 100, Nbr 10.131.63.251 on
FastEthernet0/0 from DOWN to INIT, Received Hello
6d04h: %OSPF-5-ADJCHG: Process 100, Nbr 10.131.63.251 on
FastEthernet0/0 from INIT to 2WAY, 2-Way Received
6d04h: %OSPF-5-ADJCHG: Process 100, Nbr 10.131.63.251 on
FastEthernet0/0 from 2WAY to EXSTART, AdjOK?
6d04h: %OSPF-5-ADJCHG: Process 100, Nbr 10.131.63.251 on
FastEthernet0/0 from EXSTART to EXCHANGE, Negotiation Done
6d04h: %OSPF-5-ADJCHG: Process 100, Nbr 10.131.63.251 on
FastEthernet0/0 from EXCHANGE to LOADING, Exchange Done
6d04h: %OSPF-5-ADJCHG: Process 100, Nbr 10.131.63.251 on
FastEthernet0/0 from LOADING to FULL, Loading Done

For internal use only


112
Nokia Siemens Networks

Flooding Link State Advertisements

Propagate changes to maintain Link State Database


synchronization

Flooding can impact


performance in large nets
Keep LSDB small!

For internal use only


113
Nokia Siemens Networks

Animated

Computing the Shortest Path Tree

The optimal path is determined by the


sum of the interface costs: Cost = 108/BW

Actual Network
10

Shortest Path Tree

128.213.0.0
0

10
10

128.213.0.0

10

192.213.11.0

10
5

222.211.10.0
For internal use only
114
Nokia Siemens Networks

192.213.11.0

10
5

222.211.10.0

When a Link Changes State


Router 2, Area 1
Router 1, Area 1

LSA
Link State Database
ACK

Every router in an
area hears a
specific link LSA
Each router computes
shortest path
routing table

For internal use only


115
Nokia Siemens Networks

Dijkstra Algorithm

Routing Table

Updated
Routing Table

OSPF Areas
Area is a group of contiguous
hosts and networks
Each area has a
topology database

Area 13

Area 10
Area 12

Invisible outside the area


Reduction in routing traffic
Area 0

Backbone area must be


contiguous
All other areas must

RIP/RIPv2 World

connect to the backbone

Virtual Links
For internal use only
116
Nokia Siemens Networks

Area 11

Router Types and Location

Area 13

Area 10
Area 12

Area Border Routers


Between areas

Area 0

Backbone Router (BR)


Inside the core
RIP/RIPv2
Network

Area 11

Internal Router (IR)


Inside an area
For internal use only
117
Nokia Siemens Networks

Autonomous System Boundary Routers


(ASBR) bordering a non-OSPF area

Common Types of Link State Advertisements


(LSAs)
Router link (LSA type 1)
Network link (LSA type 2)
Network summary (LSA type 3)
ASBR Summary (LSA type 4)
External (LSA type 5)
NSSA external (LSA type 7)

For internal use only


118
Nokia Siemens Networks

Simplified Example of Different LSAs

External

External (type 7)
ASBR IR
(only in NSSA)

ABR Summary (type 3)


IR ABR IR
ASBR
Area 10

ABR

Router link (type 1)


IR IR

Area 0

Network link (type 2)


DR IR

External (type 5)
ASBR IR

ABR

ASBR
DR

Area 11
ASBR

RIP Network

For internal use only


119
Nokia Siemens Networks

RIP Network

ASBR Summary (type 4)


ABR IR (about ASBR)

Note: only one example of each LSA type


exchange is demonstrated in this graphic

Animated

What is Border Gateway Protocol?


Used to exchange routing information between
networks
BGP used internally (iBGP)
AS6337
and externally (eBGP)
iBGP used to carry
AS7018

AS11268

some/all Internet prefixes


across backbone
customer prefixes

eBGP used to

AS500
AS6461

exchange prefixes with other AS's


implement routing policy
For internal use only
120
Nokia Siemens Networks

AS600

BGP Features and Characteristics


Path Vector Protocol
Incremental Updates
Many options for policy enforcement
Supports Classless Inter Domain Routing (CIDR)
Widely used for Internet backbone

For internal use only


121
Nokia Siemens Networks

What is eBGP?

Default Free Zone


Backbone ISP

Access ISP

Backbone ISP

Local NAP or IXP

Access ISP

Enterprise Networks

BGP is the routing glue that holds the entire Internet


together
For internal use only
122
Nokia Siemens Networks

Interior vs. Exterior Routing Protocols


Interior
Automatic discovery
Generally trust your IGP routers
Routes go to all IGP routers
Exterior
Specifically configured peers
Connecting with outside networks
Set administrative boundaries

For internal use only


123
Nokia Siemens Networks

What is an Autonomous System (AS)?

AS 100

Network(s) sharing the same routing policy


Possibly multiple IGPs
Usually under single ownership, trust and administrative control

Contiguous internal connectivity


Globally uniqueAS Number (1 to 65,535)
For internal use only
124
Nokia Siemens Networks

BGP Peering
BGP speakers are called peers
External
Peering

AS
100

D
E

Internal
Peering
For internal use only
125
Nokia Siemens Networks

AS 102

AS
101

Internal BGP Peering (iBGP)

AS 100
A

E
iBGP peering is between BGP speakers in the same AS
Topology independent
Not required to be directly connected but must have IGP reachability
Each iBGP speaker must peer with every other iBGP speaker in the AS
(fully meshed)
They originate connected networks
They do not pass on prefixes learned from other iBGP speakers
For internal use only
126
Nokia Siemens Networks

Stable iBGP Peering

AS 100

To implement stable iBGP peering:

Peer with loop-back address


iBGP session is not dependent on state of a single interface
iBGP session is not dependent on physical topology
Loop-back interface does not go down

For internal use only


127
Nokia Siemens Networks

External BGP Peering (eBGP)

AS 334
AS 99
Autonomous
System Border
Routers (ASBR)

Between BGP speakers in different AS


Should be directly connected
(peer with physical address)
DO NOT run an IGP between eBGP peers
For internal use only
128
Nokia Siemens Networks

Why Do We Need BGP?


Scalability
Scale a large networkDivide and Conquer
Implement hierarchy
Implement complex policies
Control reachability to prefixes
Stability
Isolate network instability
Isolate periodic IGP flooding
Simplicity
Merge separate organizations
Connect multiple IGPs

For internal use only


129
Nokia Siemens Networks

How Does BGP Work?


Learns multiple paths via internal and external BGP speakers
and stores them
Picks THE best path, installs it in the IP forwarding table
Forwards all best paths to eBGP neighbors
Forwards external and locally originated best paths to iBGP
neighbors
Path selection is influenced by applying policies

For internal use only


130
Nokia Siemens Networks

Constructing the Forwarding Table

everything

in

All
BGP
peers

out

For internal use only


131
Nokia Siemens Networks

discarded

BGP
IN
process

accepted
Other
protocols

Best Path
selection
algorithm

BGP
OUT
process

BGP
table

forwarding
table

best paths

Animated

How Does BGP Advertise Routes?

AS101

AS100
A

Both peers attempt to connectthere is an algorithm to


resolve connection collisions
Exchange messages to open and confirm the connection
parameters
Initially peers exchange entire table
Only incremental updates after initial exchange
Keep alive messages exchanged when there no updates
BGP messages exchanged using TCP (port 179)
For internal use only
132
Nokia Siemens Networks

What are the Basic BGP Messages?


KEEPALIVE:
keeps connection alive in absence of UPDATES; also ACKs OPEN
request

NOTIFICATION:
reports errors in previous msg; also used to close connection
Example: peer in wrong AS
OPEN:
opens TCP connection to peer and authenticates sender
Exchange AS, router ID, holdtime
Capability negotiation
UPDATES (incremental):
advertises new path (or withdraws old)

For internal use only


133
Nokia Siemens Networks

BGP States

3 Active

2 Connect

-1 PFXCD

OPEN

4 OpenSent
1 Idle

KEEPALIVE

5 OpenConfirm

6 Established
For internal use only
134
Nokia Siemens Networks

KEEPALIVE
UPDATE

0 Shutdown

Reference Point 5: MPLS (Multi Protocol


Label Switching)

For internal use only


135
Nokia Siemens Networks

The Barriers

Frame Relay and ATM services are


available:

Carriers customers want IP services:

They provide connection-

IP services
They need more flexible IP
quality of service
guarantees
They need more privacy
than the Internet provides

oriented service
They have inflexible pointto-point bandwidth
guarantees
But they have good privacy
For internal use only
136
Nokia Siemens Networks

They need connectionless

The Solution - MPLS


MULTI-PROTOCOL LABEL SWITCHING
A mechanism that delivers the best of both worlds:
PRIVACY and QOS of ATM, Frame Relay
FLEXIBILITY and SCALABILITY of IP
Foundation for IP business services
Flexible grouping of users and value-added services
Low cost managed IP services
scales to large and small private networks

For internal use only


137
Nokia Siemens Networks

What Is MPLS?
Multi Protocol Label Switching
MPLS is an efficient encapsulation mechanism
Uses labels appended to packets (IP packets, AAL5 frames) for
transport of data
MPLS packets can run on other Layer 2 technologies such as ATM,
FR, PPP, POS, Ethernet
Other Layer 2 technologies can be run over an
MPLS network
Labels can be used as designators
For exampleIP prefixes, ATM VC, or a bandwidth
guaranteed path

MPLS is a technology for delivery of IP services

For internal use only


138
Nokia Siemens Networks

MPLS as a Foundation for


Value-Added Services

Provider
Provisioned
VPNs

Traffic
Engineering

IP+ATM

IP+Optical
GMPLS

MPLS

Network Infrastructure

For internal use only


139
Nokia Siemens Networks

Any
Transport
over MPLS

MPLS concepts

Packet forwarding is done based on labels


Labels assigned when the packet enters the network
Labels inserted between layer 2 and layer 3 headers
MPLS nodes forward packets based on the label
Separates ROUTING from FORWARDING
Routing uses IP addresses
Forwarding uses Labels
Labels can be stacked

For internal use only


140
Nokia Siemens Networks

MPLS Concepts
In Core:
Forward using labels
(as opposed to IP addr)
Label indicates service class
and destination
Label swapping or switching

At Edge:
Classify packets
Label them
Label imposition

At Edge:
Remove labels and forward
packets
Label disposition

Edge Label Switch


Router
(ATM Switch or
Router)

Label Distribution Protocol

Label Switch Router (LSR)


Router
ATM switch + label
switch controller

Create new services via flexible classification


Provide the ability to setup bandwidth guaranteed paths
Enable ATM switches to act as routers
For internal use only
141
Nokia Siemens Networks

MPLS Operation
1a. Existing Routing Protocols (e.g. OSPF, IS-IS)
Establish Reachability to Destination Networks
1b. Label Distribution Protocol (LDP)
Establishes Label to Destination
Network Mappings

2. Ingress Edge LSR Receives Packet,


Performs Layer 3 Value-Added Services,
and Labels Packets
For internal use only
142
Nokia Siemens Networks

4. Edge LSR at
Egress Removes
Label and Delivers
Packet

3. LSR Switches Packets


Using Label Swapping

Label Encapsulation

Packet over SONET/SDH


Ethernet
Frame Relay PVC
ATM PVCs
Subsequent cells

PPP

Label

IP header

Data

Ethernet

Label

IP Header

Data

Frame Relay

Label

IP Header

Data

ATM Header

Label

IP Header

Data

ATM Header

Data

F
R
A
M
E

Label
ATM label switching

GFC VPI

VCI

PTI

CLP HEC IP Header

Subsequent cells

GFC VPI

VCI

PTI

CLP HEC Data

Label
For internal use only
143
Nokia Siemens Networks

Data

C
E
L
L

Label Header (Shim)

Bit

8
1

Label

EXP

S3
4

TTL
Label
EXP
S
TTL

Byte

Label Value (20 bits)


Class of Service (3 bits)
Bottom of Stack (1 bit)
Time to Live

Can be used over Ethernet, 802.3, or PPP links


Ethertype 0x8847
One for unicast, one for multicast
Four octets per label in stack
For internal use only
144
Nokia Siemens Networks

Relevant MPLS Capabilities

The ability to FORWARD on and STACK LABELS allows


MPLS to provide some useful features including:
IP+ATM Integration
Provides Layer 3 intelligence in ATM switches
Virtual Private Networks
Layer 3 Provider has knowledge of customer routing
Layer 2 Provider has no knowledge of customer
routing
Traffic Engineering
Force traffic along predetermined paths

For internal use only


145
Nokia Siemens Networks

MPLS VPN Layer 3


Private, connectionless IP VPNs
Outstanding scalability
Customer IP addressing freedom
Multiple QoS classes
Secure support for intranets and
extranets
Easy to provide Intranet/Extranet/3rd
Party ASP
Support over any access or backbone
technology

Connection-Oriented
VPN Topology

VPN B

VPN A
VPN C
VPN B

VPN C

VPN A
VPN A

VPN B
VPN C

Connectionless
VPN Topology

VPN C
VPN B

VPN A

VPN B

VPN A
VPN C

VPN C

VPN B

VPN A

Determines VPN on
PE Router

IP Packet
For internal use only
146
Nokia Siemens Networks

VPN
Label

Determines PE
Router

IGP
Label

VPN A
VPN B
VPN C

VPN C
VPN A

VPN B

MPLS VPN Layer 2


 Additional Capabilities:
Virtual leased line service
Offer PVC-like Layer 2-based
service

L2 Pseudowire/Emulated VC

 Reduced costconsolidate
multiple core technologies
into a single packet-based
network infrastructure

L2 Frames
Attachment
Circuit
Attachment
Circuit

 Simpler provisioning of L2
services
 Attractive to Enterprise that
wish keep routing private
Determines VC inside
the tunnel

L2 Frame
For internal use only
147
Nokia Siemens Networks

VC
Label

Determines PE
Router end point

Tunnel
Label

Why Providers like MPLS VPN


Separately engineered
private IP networks

vs

Single network
supporting multiple VPNs

MPLS VPN
Network

Build once,
Sell once

For internal use only


148
Nokia Siemens Networks

Build once,
Sell many

Traffic Engineering
Why traffic engineer?
Optimise link utilisation
Specific paths by customer or class
Balance traffic load
Traffic follows pre-specified path
Path differs from normally routed path
Controls packet flows across a L2 or L3
network

Determines LSP next


hop contrary to IGP

IP Packet
For internal use only
149
Nokia Siemens Networks

VPN
Label

IGP
Label

TE
Label

Route chosen by
IP routing protocol

Route specified by
traffic engineering

MPLS Components
Edge Label Switching Routers (ELSR or PE)
Label previously unlabeled packets - at the beginning of a
Label Switched Path (LSP)
Strip labels from labeled packets - at the end of an LSP
Label Switching Routers (LSR or P)
Forward labeled packets based on the information carried by
labels

For internal use only


150
Nokia Siemens Networks

MPLS Forwarding Operations


Label Imposition: add label stack to unlabeled packet (e.g. IP
packet) at edge (push)
Label Forwarding: use label on packet to select next hop and
label stack operation (replace, replace & push)
Label Disposition: Remove (last) label from packet (pop)

For internal use only


151
Nokia Siemens Networks

Summary
MPLS allows flexible packet classification and network
resources optimisation
Labels are distributed by different protocols
LDP, RSVP, BGP
Different distribution protocols may co-exist in the same LSR
Labels have local (LSR) significance
No need for global (domain) wide label allocation/numbering

For internal use only


152
Nokia Siemens Networks

Benefits of MPLS
De-couples IP packet forwarding from the information carried in
the IP header of the packet
Provides multiple routing paradigms (e.g., destination-based,
explicit routing, VPN, multicast, CoS, etc) over a common
forwarding algorithm (label swapping)
Facilitates integration of ATM and IP - from control plane point
of view an MPLS-capable ATM switch looks like a router

For internal use only


153
Nokia Siemens Networks

RFC 2547: MPLS VPNs

CE
CE

iBGPVPNv4
Label Exchange

VRF

LDP

LDP

VRF

LDP

PE

PE
iBGPVPNv4

iBGPVPNv4
PE

CE
CE
For internal use only
154
Nokia Siemens Networks

Overlapping Addresses Are


Made Unique by Appending RD
and Creating VPNv4 Addresses

VRF

CE

What is an MPLS-VPN?
An IP network infrastructure delivering private network services
over a public infrastructure
Use a layer 3 backbone
Scalability, easy provisioning
Global as well as non-unique private address space
QoS
Controlled access
Easy configuration for customers

For internal use only


155
Nokia Siemens Networks

VPN Models
There are two basic types of design models that deliver VPN
functionality
Overlay Model
Peer Model

For internal use only


156
Nokia Siemens Networks

MPLS-VPN = True Peer model

MPLS-VPN is similar in operation to peer model


Provider Edge routers receive and hold routing information
only about VPNs directly connected
Reduces the amount of routing information a PE router will
store
Routing information is proportional to the number of VPNs
a router is attached to
MPLS is used within the backbone to switch packets (no
need of full routing)

For internal use only


157
Nokia Siemens Networks

MPLS VPN Connection Model

A VPN is a collection of sites sharing a common routing


information (routing table)
A site can be part of different VPNs
A VPN has to be seen as a community of interest (or
Closed User Group)
Multiple Routing/Forwarding instances (VRF) on PE

For internal use only


158
Nokia Siemens Networks

MPLS VPN Connection Model

Site-4
Site-1

VPN-C

VPN-A
Site-3

Site-2

VPN-B

A site belonging to different VPNs may or MAY NOT be


used as a transit point between VPNs
If two or more VPNs have a common site, address space
must be unique among these VPNs
For internal use only
159
Nokia Siemens Networks

MPLS VPN Connection Model

The VPN backbone is composed by MPLS LSRs


PE routers (edge LSRs)
P routers (core LSRs)
The customer router connecting to the VPN backbone is
called the Customer Edge (CE)
PE routers are faced to CE routers and distribute VPN
information through MP-BGP to other PE routers
VPN-IPv4 addresses, Extended Community, Label

P routers do not run MP-BGP and do not have any VPN


knowledge

For internal use only


160
Nokia Siemens Networks

PE-CE Routing
CE1
PE
CE2

PE-CE routing

PE and CE routers exchange routing information through eBGP,


Static, OSPF, ISIS, RIP, EIGRP
The CE router runs standard routing software, not aware it is
connected to a VPN network

For internal use only


161
Nokia Siemens Networks

Routing Protocol Contexts

BGP

Routing
processes

RIP

Static
 Routing processes run within
specific routing contexts

Routing
contexts

BGP
1

BGP
2

BGP
3

RIP
1

 Populate specific VPN routing


table and FIBs (VRF)

RIP
2

 Interfaces are assigned to VRFs


VRF Routing
tables
VRF Forwarding
tables

For internal use only


162
Nokia Siemens Networks

VRF
Site A

VRF
Site B

VRF
Site C

Routing Tables
CE1

VRF

PE
CE2

PE-CE routing

VPN Backbone IGP (OSPF, ISIS)

Global Routing Table

PE routers maintain separate routing tables


Global Routing Table
All the PE and P routes populated by the VPN backbone IGP (ISIS or
OSPF)

VPN Routing and Forwarding Tables (VRF)


Routing and Forwarding table associated with one or more directly
connected sites (CEs)
VRF are associated to (sub/virtual/tunnel) interfaces
Interfaces may share the same VRF if the connected sites may share the
same routing information
For internal use only
163
Nokia Siemens Networks

Route-Target and Route-Distinguisher


update X

CE1

update X

P1

PE1

P2

CE3

PE2

CE2

CE4

x
MP-iBGP session
update X

update X

VPN-IPv4 update:
RD1:X, Next-hop=PE1
RT=RED, Label=10

VPN-IPv4 update:
RD2:X, Next-hop=PE1
RT=ORANGE, Label=12

VPN-IPv4 updates are


translated into IPv4
address and inserted into
the VRF corresponding to
the RT value

MP-BGP prepends an Route Distinguisher (RD) to each


VPN route in order to make it unique
MP-BGP assign a Route-Target (RT) to each VPN route to
identify VPN it belongs to (or CUG)
Route-Target is the colour of the route
For internal use only
164
Nokia Siemens Networks

Route Propagation through MP-BGP


update X

CE1

update X

P1

PE1

P2

CE3

PE2

CE2

CE4

x
MP-iBGP session
update X

update X

VPN-IPv4 update:
RD1:X, Next-hop=PE1
RT=RED, Label=10

VPN-IPv4 update:
RD2:X, Next-hop=PE1
RT=ORANGE, Label=12

VPN-IPv4 updates are


translated into IPv4
address and inserted into
the VRF corresponding to
the RT value

When a PE router receives an MP-BGP VPN route:


It checks the route-target value to VRF route-targets
If match then route is inserted into appropriate VRF
The label associated with the VPN route is stored and
used to send packets towards the destination
For internal use only
165
Nokia Siemens Networks

Multi-Protocol BGP
Propagates VPN routing information
Customer routes held in VPN Routing and Forwarding tables
(VRFs)
Only runs on Provider Edge
P routers are not aware of VPNs only labels
PEs are fully meshed
Using Route Reflectors or direct peerings between PE routers

For internal use only


166
Nokia Siemens Networks

MPLS VPN Protocols

OSPF/IS-IS
Used as IGP provides reachability between all Label
Switch Routers (PE <-> P <-> PE)
TDP/LDP
Distributes label information for IP destinations in core
MP-BGP4
Used to distribute VPN routing information between PEs
RIPv2/BGP/OSPF/eiGRP/ISIS/Static
Can be used to route between PE and CE

For internal use only


167
Nokia Siemens Networks

VPN Components

VRF Tables
Hold customer routes at PE
Route-Distinguisher
Allows MP-BGP to distinguish between identical
customer routes that are in different VPNs
Route-Targets
Used to import and export routes between different VRF
tables (creates Intranets and Extranets)
Route-maps
Allows finer granularity and control of importing
exporting routes between VRFs instead of just using
route-target
For internal use only
168
Nokia Siemens Networks

MPLS VPN Operation


CE

= RT?

RD +
RD +
VPN labels, RTs

PE
P

RR

Si

RD +

PE

PE

RD +
RD +
VPN labels, RTs

Import routes into VRF if route-targets match (export = import)


Customer routes placed into separate VRF tables at each PE
IGP (OSPF,ISIS) used to establish reachability to destination networks.
Label Distribution Protocol establishes mappings to IGP addresses
CE-PE dynamic routing (or static) populate the VRF routing tables
MP-BGP between PE router to distribute routes between VPNs

For internal use only


169
Nokia Siemens Networks

CE

Si

RR

PE
CE

= RT?

CE

MPLS VPN Label Stack


There are at least two labels when using MPLS-VPN
The first label is distributed by TDP/LDP
Derived from an IGP route
Corresponds to a PE address (VPN egress point)
PE addresses are MP-BGP next-hops of VPN routes
The second label is distributed MP-BGP
Corresponds to the actual VPN route
Identifies the PE outgoing interface or routing table

L2 Header Label 1
For internal use only
170
Nokia Siemens Networks

Label 2

L3 Header Data

Frame, e.g. HDLC, PPP, Ethernet

MPLS VPN Forwarding


Example

CE

CE
PE

PE
P

CE

Si

P
CE

Si

PE

PE

Swap IGP Label


(From LFIB)

POP IGP Label


(Pentultimate Hop)

Push VPN Label


(Red Route)

For internal use only


171
Nokia Siemens Networks

Push IGP Label


(Green PE Router)

Pop VPN Label


(Red Route)

Motivation for Traffic Engineering


Increase efficiency of bandwidth resources
Prevent over-utilised (congested) links whilst other links are
under-utilised
Ensures the most desirable/appropriate path for certain traffic
types based on certain policies
Override the shortest path selected by the IGP
The ultimate goal is COST SAVING

For internal use only


172
Nokia Siemens Networks

The Fish Problem (Shortest Path)

R3
R8

R4
R5

R2

R1
R6

IP uses shortest path destination-based routing


Shortest path may not be the only path
Alternate paths may be under-utilized
Whilst the shortest path Is over-utilized
For internal use only
173
Nokia Siemens Networks

R7

Shortest Path and congestion


20Mbps
traffic to R5

60Mbps
aggregate

R3

26Mbps
drops!

R8

R4
OC3
(155Mbps)

R2

R1

For internal use only


174
Nokia Siemens Networks

R5
GigE
(1Gbps)

GigE
(1Gbps)

R6
40Mbps
traffic to R5

E3
(34Mbps)

OC3
(155Mbps)

GigE
(1Gbps)

R7

The TE solution
20Mbps
traffic to R5

R3

R8

20Mbps traffic
to R5 from R8
R4
R5

R2

40Mbps traffic
to R1 from R8

R1
R6
40Mbps
traffic to R5
MPLS Labels can be used to engineer explicit paths
Tunnels are UNI-DIRECTIONAL
Normal path: R8  R2  R3  R4  R5
Tunnel path: R1  R2  R6  R7  R4

For internal use only


175
Nokia Siemens Networks

R7

Terminology
Constrained-Based Shortest Path First (CSPF)
MPLS-TE uses CSPF to create a shortest path
based on a series of constraints:
Bandwidth
Affinity/Link Attributes
Priority

Tunnels are UNI-DIRECTIONAL!


HEADEND

Upstream

For internal use only


176
Nokia Siemens Networks

MIDPOINT

Tunnel Direction

TAILEND

Downstream

Traffic Engineering Components


Information distribution
Path selection/calculation
Path setup
Trunk admission control
Path maintenance
Forwarding traffic on to tunnel

For internal use only


177
Nokia Siemens Networks

What is Quality of Service?


From a technical perspective
QoS represents the set of techniques necessary to
manage network bandwidth, delay, jitter, and packet loss.
From a business perspective - MANAGED FAIRNESS
.
Critical applications are guaranteed
network resources
required, despite varying network traffic load The ability
to enable predictive response to application traffic

For internal use only


178
Nokia Siemens Networks

Motivation

Offer Differentiated Services


Premium-Class Service (VoIP, Stock Quotes)
Business-Class Service (SAP, Oracle, Citrix)
Best-Effort Service (Backups, Email)
Support for Multi-Service Networks
Supporting Triple Play Services
Voice, Video, Data over IP

For internal use only


179
Nokia Siemens Networks

QoS and MPLS


MPLS does NOT define a new QoS architecture
MPLS QoS uses Differentiated Services (DiffServ) architecture
defined for IP QoS
DiffServ Architecture defined in RFC2475
MPLS support for DiffServ defined in RFC3270
Class of Service Classification carried in
COS Field of Ethernet VLAN 802.1p
TOS Byte of IP Header
DSCP Field of IP Header
EXP Field of MPLS Header

For internal use only


180
Nokia Siemens Networks

Type of Service Field in IP Header


TOS is 8 bit field (1 byte) in the IP header
Same byte is re-defined as the DSCP

0
0

Version

Prec

00

Header
Length

1
0

Type-of-Service

Identification
Time-to-live

Total Length
Flags

Protocol

Offset
Header Checksum

Source IP Address
Destination IP Address
Options and Padding
For internal use only
181
Nokia Siemens Networks

2
0

3
0

EXP Field in MPLS Header

EXP is 3 bit field MPLS Label Header (also known as SHIM)

LABEL
0
0

For internal use only


182
Nokia Siemens Networks

1
0

EXP

2
0

TTL

3
0

IETF DiffServ Model


Re-define TOS byte in IP header to Differentiated Services
Code Point (DSCP) or DS Byte
Uses 6 bits to categorise traffic into Behavior Aggregates or
Classes
Defines a number of Per Hop Behaviors applied to links
Two-Ingredient Recipe:

Condition the Traffic at the Edges


Invoke the PHBs in the Core

For internal use only


183
Nokia Siemens Networks

Differentiated Services Architecture (RFC 2745)


DiffServ Domain

DiffServ Domain
Ingress
Node

TCA
PHB

DiffServ Domain

Interior
Node

Egress
Node

PHB

TCA
PHB

Traffic Conditioning Agreement (TCA)

Per-Hop Behavior (PHB)

Classification/Marking/Policing/Shaping

Queuing/Dropping

For internal use only


184
Nokia Siemens Networks

DiffServ Terminology

PHB
Per Hop Behavior
The DiffServ treatment (scheduling/dropping) applied by a Router to all the
packets which are to experience the same DiffServ service

DSCP Differentiated Services Code Point


The value in the IP Header indicating which PHB is to be applied to the
packet

BA
Behaviour Aggregate
The set of all the packets which have the same DSCP (and thus that will
receive the same PHB)

OA
Ordered Aggregate
The set of BAs which have an ordering constraint (must go into the same
queue)

PSC
PHB Scheduling Class
The set of PHBs applied to an OA (the set of PHBs using the same
queue)

For internal use only


185
Nokia Siemens Networks

DiffServ Terminology - How they fit together


OA

Packets with AF
markings

PSC

BA AF11

PHB

BA AF12

PHB

BA AF13

PHB

OA

Packets with AF
markings

Queue for AF1x


(Bronze Class)

PSC

BA AF21

PHB

BA AF22

PHB

BA AF23

PHB

For internal use only


186
Nokia Siemens Networks

Drop Probabilities
within the queue

Link

Queue for AF2x


(Sliver Class)

Per-Hop Behaviors (PHB)


Expedited Forwarding (EF)
Building block for low delay/jitter/loss
Served at a certain rate with short/empty queues
Assured Forwarding (AF)
High probability of delivery if profile is not exceeded
Four classes and three levels of drop precedence
Specific resources (BW, buffer space) allocated to each class
at each node
Best Effort (BE)

For internal use only


187
Nokia Siemens Networks

DiffServ Classes (DSCP Values)

Priority Classes
High

Low
EF

AF4

AF3

AF2

AF1

BE

Low
Drop Probability

Priority 101110 (46)


Low Drop
AFx1

AF41
100010 (34)

AF31
011010 (26)

AF21
010010 (18)

AF11
001010 (10)

Med Drop
AFx2

AF42
100100 (36)

AF32
011100 (28)

AF22
010100 (20)

AF12
001100 (12)

High Drop
AFx3

AF43
100110 (38)

AF33
011110 (30)

AF23
010110 (22)

AF13
001110 (14)

Best
Effort

High

For internal use only


188
Nokia Siemens Networks

000000

Reference Point 6: IP Evolution IPv6 &


Strategy

For internal use only


189
Nokia Siemens Networks

An IPv4 packet walks into a bar and says Give me a CIDR,


Im exhausted
An IPv6 packet walks into a bar and complains I cant get a
drink because not many people understand me

For internal use only


190
Nokia Siemens Networks

The Day The Earth Stood Still

Hey Buddy,
Can you spare
an IPv4 address?

3rd February 2011


The last five remaining /8 pools were allocated amongst the
five Regional Internet Registries

Announcement by ICCAN
Available Pool of Unallocated IPv4 Internet Addresses Now
Completely Emptied
For internal use only
Source:
http://www.icann.org/en/news/releases/release-03feb11-en.pdf
191
Nokia
Siemens Networks

Where Did All the IPv4 Go?


000
IANA

001
APNIC

014
PDN

015
HP

016
DEC

019
Ford

020
CsC

021
US DoD

234
Multicast

235
Multicast

236
Multicast

239
Multicast

240
Class E

241
Class E

254
Class E

255
Class E

003
GE

002
RIPE

013
Xerox

012
AT&T

017
Apple

018
MIT

023
Next

022
US DoD

233
Multicast

232
Multicast

237
Multicast

238
Multicast

243
Class E

242
Class E

253
Class E

252
Class E

004
L3

007
ARIN

008
L3

011
US DoD

030
US DoD

029
US DoD

024
Cable

025
230
UK Defense Multicast

231
Multicast

226
Multicast

225
Multicast

244
Class E

247
Class E

248
Class E

251
Class E

005
RIPE

006
US DoD

009
IBM

010
RFC1918

031
RIPE

028
US DoD

027
APnic

026
US DoD

229
Multicast

228
Multicast

227
Multicast

224
Multicast

245
Class E

246
Class E

249
Class E

250
Class E

058
APnic

057
SITA

054
Merck

053
Cap Debis

032
AT&T

035
MERIT

036
APnic

037
RIPE

218
APnic

219
APnic

220
APnic

223
APnic

202
APnic

201
LACnic

198
Legacy

197
AFRINic

059
APnic

056
US Postal

055
US DoD

052
033
El duPONT US DoD

034
Haliburton

039
APnic

038
PSI

217
RIPE

216
ARIN

221
APnic

222
APnic

203
APnic

200
LACnic

199
ARIN

196
AFRInic

060
APnic

061
APnic

050
ARIN

051
UK DSS

046
RIPE

045
ARIN

040
Eli Lily

041
AFRInic

214
US DoD

215
US DoD

210
APnic

209
ARIN

204
ARIN

205
ARIN

194
RIPE

195
RIPE

063
ARIN

062
RIPE

049
APnic

048
Prudential

047
Bell North

044
Radio

043
Inet

042
APnic

213
RIPE

212
RIPE

211
APnic

208
ARIN

207
ARIN

206
ARIN

192
RIPE

192
Legacy

064
ARIN

067
ARIN

068
ARIN

069
ARIN

122
APnic

123
APnic

124
APnic

127
Loopback

128
Legacy

131
Legacy

132
Legacy

133
Legacy

186
LACnic

187
LACnic

188
Legacy

191
Legacy

065
ARIN

066
ARIN

071
ARIN

070
ARIN

121
APnic

120
APnic

125
APnic

126
APnic

129
Legacy

130
Legacy

135
Legacy

134
Legacy

185
RIPE

184
ARIN

189
LACnic

190
LACnic

078
RIPE

077
RIPE

072
ARIN

073
ARIN

118
APnic

119
APnic

114
APnic

113
APnic

142
Legacy

141
Legacy

136
Legacy

137
Legacy

182
APnic

183
APnic

178
RIPE

177
LACnic

079
RIPE

076
ARIN

075
ARIN

074
ARIN

117
APnic

116
APnic

115
APnic

112
APnic

143
Legacy

140
Legacy

139
Legacy

138
Legacy

181
LACnic

180
APnic

179
LACnic

176
RIPE

080
RIPE

081
RIPE

094
RIPE

095
RIPE

096
ARIN

097
ARIN

110
APnic

111
APnic

144
Legacy

145
Legacy

158
Legacy

159
Legacy

160
Legacy

161
Legacy

174
ARIN

175
APNIC

083
RIPE

082
RIPE

093
RIPE

092
RIPE

099
ARIN

098
ARIN

109
RIPE

108
ARIN

147
Legacy

146
Legacy

157
Legacy

156
Legacy

163
Legacy

162
Legacy

173
ARIN

172
Legacy

084
RIPE

087
RIPE

088
RIPE

091
RIPE

100
ARIN

103
APnic

104
ARIN

107
ARIN

148
Legacy

151
Legacy

152
Legacy

155
Legacy

164
Legacy

167
Legacy

168
Legacy

171
Legacy

090
RIPE

101
APnic

102
AFRInic

105
AFRInic

106
APnic

149
Legacy

150
Legacy

153
Legacy

154
Legacy

165
Legacy

166
Legacy

169
Legacy

170
Legacy

085use only086
For internal
089
RIPE
RIPE
RIPE
192
Nokia Siemens
Networks

It Is Not Just About IPv4 Exhaustion


There are arguably two intertwined problems
Exhaustion of Global and Private IPv4 address space
Addressed by IPv6 and stop gap measures such as NAT, CIDR
Available AS number pool also shrinking (hence 32 bit AS numbers)
Private RFC1918 space is not big enough for many SPs
Growing size of the Internet routing table
July 2010

Feb 2011

IPv4 BGP Entries

328,598

350,103

IPv6 BGP Entries

3114

4752

As IPv6 grows aggregation is desirable (PI vs PA)

For internal use only


http://bgp.potaroo.net
193
Source:
Nokia Siemens
Networks

APNIC R&D 25 Feb 2011

What Are The Drivers To Move To IPv6?


IPv6 is an enabler
It is NOT a new service
It allows anything to connect to
everything

For internal use only


194
Nokia Siemens Networks

IPv4 address pool exhausted


NGN Capabilities to Defence
Government Mandates
Cable market address scaling
Population densities in APAC
4G deployments
Smart Grids/Sensor Networks
Connected Communities
IPv4 connects computers
IPv6 connects people and things

Technical Benefits of IPv6


Huge address space
Simplified header format
Efficient packet handling fields moved out of header or

eliminated
Checksum removed, Fragmentation moved to end hosts
Hierarchical network architecture
Routing efficiency high level of aggregation possible
Auto configuration and plug-and-play support
Some reduction in the need for network address translation
Optimized for Internet mobile applications
New types of peer to peer applications
Increased number of multicast addresses
Flow labels for QoS

For internal use only


195
Nokia Siemens Networks

IPv4 and IPv6 Header Comparison


IPv4 Header
Version IHL

Type of
Service

Identification
Time to Live

Total Length
Version
Flags

Protocol

IPv6 Header

Fragment
Offset

Header Checksum

Traffic
Class

Flow Label

Payload Length

Source Address
Destination Address

Legend

Options

Padding

Source Address

Fields Name Kept from IPv4 to IPv6


Fields Not Kept in IPv6
Name and Position Changed in IPv6
New Field in IPv6

For internal use only


196
Nokia Siemens Networks

Destination Address

Next
Header

Hop Limit

IPv6 Addresses
IPv6 addresses are 128 bits long
Segmented into 8 groups of four HEX characters
Separated by a colon (:)
50% for network ID, 50% for interface ID
Network portion is allocated by Internet registries 2^64 (1.8 x 1019)
Still leaves us with ~ 3 billion network prefixes for each person on earth
Global Unicast Identifier Example

Network Portion

Interface ID

gggg:gggg:gggg:s
ssssxxxx:xxxx:xxxx:
sss:
:xxxx
Global Routing Subnet ID
64 n bits
Prefix
n <= 48 bits

Host

2001:0000:0000:0
00A10000:0000:0000:
0A1:
:1E2A

For internal use only


197
Nokia Siemens Networks

2001:0: A1:
:1E2A
0:

Full Format

Abbreviated Format

Integration or Migration?
Application
Migration

IPv6 + IPv4
Integration

PE

IPv
6

Application
Migration

PE
CE

CE
IPv4+IPv6
Core

IPv
6

 Some applications at the edge will MIGRATE to IPv6


 Network infrastructures will INTEGRATE IPv6
IPv4 will be around for a very long time
Networks will support both protocols
Many hardware components will be dual-stack capable (IPv4+IPv6)
IPv6 is a gradual and controlled process of INTEGRATION
For internal use only
198
Nokia Siemens Networks

IPv6 Planning Steps


Business Case Identified/Justified

Evaluate effect
on business
model

Establish IPv6
project
management
team

IPv6 Training
strategy

Decide IPv6
architectural
solution

Test
application
software and
services

Develop
procurement
plan
For internal use only
199
Nokia Siemens Networks

Assess
network
hardware and
software

Obtain IPv6
prefix(es)

Develop IPv6
exception
strategy

Develop
security
policy

10

IPv6 Deployment Options


IPv6 Only

IPv6 is the only protocol operating in the network


IPv6

IPv6

IPv6

 Dual Stack (in devices/hosts and networks)


IPv4 and IPv6 operate in tandem over shared or dedicated links
Applications Dual
Stack Aware

IPv4
IPv6

IPv4
IPv6

IPv6

IPv4

IPv4

 Tunnelling over IPv4 or MPLS

Shared
Links

IPv6

Dedicated Links

IPv6 confined to the edge of the IPv4 / MPLS core


IPv6

IPv4/MPLS

IPv4/MPLS

Tunnel

 Protocol Translation (Moving to Experimental in IETF)


Allow IPv6-only devices to communicate with IPv4-only devices
For internal use only
200
Nokia Siemens Networks

Thank You!

For internal use only


201
Nokia Siemens Networks

Potrebbero piacerti anche