ppp (point to point protocol)

PPP (Point to Point Protocol)

W.lilakiatsakun

Introduction to PPP (1)

• PPP encapsulates data frames for transmission over Layer 2 physical links including following features:– The link quality management feature monitors the

quality of the link. If too many errors are detected, PPP takes the link down.

– PPP supports PAP and CHAP authentication.

Introduction to PPP (2)

PPP Component (1)

• HDLC protocol for encapsulating datagrams over point-to-point links.

• Extensible Link Control Protocol (LCP) to establish, configure, and test the data link connection.

PPP Component (2)

• Family of Network Control Protocols (NCPs) for establishing and configuring different Network layer protocols. – PPP allows the simultaneous use of multiple

Network layer protocols. – Some of the more common NCPs are Internet

Protocol Control Protocol, Appletalk Control Protocol, Novell IPX Control Protocol, Cisco Systems Control Protocol, SNA Control Protocol, and Compression Control Protocol.

PPP Architecture (1)


• At the Physical layer, you can configure PPP on a range of interfaces, including:– Asynchronous serial (RS-232)– Synchronous serial (RS422/V.35)– HSSI (High Speed Serial Interface)– ISDN


• The LCP has a role in establishing, configuring, and testing the data-link connection.

• The LCP provides automatic configuration of the interfaces at each end, including:– Handling varying limits on packet size – Detecting common misconfiguration errors – Terminating the link – Determining when a link is functioning properly or

when it is failing


• PPP permits multiple Network layer protocols to operate on the same communications link. – For every Network layer protocol used, PPP uses a

separate NCP. – For example, IP uses the IP Control Protocol

(IPCP), and IPX uses the Novell IPX Control Protocol (IPXCP)


• NCPs include functional fields containing standardized codes to indicate the Network layer protocol that PPP encapsulates.

PPP Frame Structure (1)

Establish PPP Session (1)


• Phase 1: Link establishment and configuration negotiation – Before PPP exchanges any Network layer

datagrams (for example, IP), the LCP must first open the connection and negotiate configuration options.

– This phase is complete when the receiving router sends a configuration-acknowledgment frame back to the router initiating the connection.


• Phase 2: Link quality determination (optional) – The LCP tests the link to determine whether the

link quality is sufficient to bring up Network layer protocols.

– The LCP can delay transmission of Network layer protocol information until this phase is complete


• Phase 3: Network layer protocol configuration negotiation – After the LCP has finished the link quality

determination phase, the appropriate NCP can separately configure the Network layer protocols, and bring them up and take them down at any time.

– If the LCP closes the link, it informs the Network layer protocols so that they can take appropriate action.

LCP Operation (1)

LCP Operation (2)

LCP Operation (3)

PPP Configuration Option (1)

• PPP can be configured to support various functions including:– Authentication using either PAP or CHAP– Compression using either Stacker or Predictor– Multilink which combines two or more channels

to increase the WAN bandwidth

NCP Process (1)

NCP Process (2)

• IPCP negotiates two options:– Compression • Allows devices to negotiate an algorithm to compress

TCP and IP headers and save bandwidth. • Van Jacobson TCP/IP header compression reduces the

size of the TCP/IP headers to as few as 3 bytes. • This can be a significant improvement on slow serial

lines, particularly for interactive traffic.

NCP Process (3)

– IP-Address • Allows the initiating device to specify an IP address to

use for routing IP over the PPP link, or to request an IP address for the responder. • Dialup network links commonly use the IP address

option.

PPP Authentication Protocol (1)

• The authentication phase of a PPP session is optional.– If it is used, you can authenticate the peer after the

LCP establishes the link and choose the authentication protocol.

– If it is used, authentication takes place before the Network layer protocol configuration phase begins.

– RFC 1334 defines two protocols for authentication, PAP and CHAP

PPP Authentication Protocol (2)

PAP (Password Authentication Protocol) (1)

• PAP provides a simple method for a remote node to establish its identity using a two-way handshake.

• PAP is not a strong authentication protocol. Using PAP, you send passwords across the link in clear text and there is no protection from playback or repeated trial-and-error attacks.

PAP (Password Authentication Protocol) (2)

CHAP (Challenge Handshaking Authentication Protocol) (1)

• Unlike PAP, which only authenticates once, CHAP conducts periodic challenges to make sure that the remote node still has a valid password value.

• The remote node responds with a value calculated using a one-way hash function, which is typically Message Digest 5 (MD5) based on the password and challenge message.

Initiating CHAP

Responding CHAP

Completing CHAP


• CHAP provides protection against playback attack by using a variable challenge value that is unique and unpredictable.– Because the challenge is unique and random, the

resulting hash value is also unique and random.

PPP Authentication Process


• Authentication – Peer routers exchange authentication messages. – Two authentication choices are Password

Authentication Protocol (PAP) and Challenge Handshake Authentication Protocol (CHAP).


• Compression – Increases the effective throughput on PPP

connections by reducing the amount of data in the frame that must travel across the link.

– The protocol decompresses the frame at its destination.

– Two compression protocols available in Cisco routers are Stacker and Predictor. http://www.cisco.com/en/US/tech/tk713/tk802/technologies_tech_note09186a00801b3b86.shtml

http://www.cisco.com/en/US/tech/tk713/tk802/technologies_tech_note09186a00801b3b86.shtml

http://www.cisco.com/en/US/tech/tk713/tk802/technologies_tech_note09186a00801b3b86.shtml


• Error detection – The Quality and Magic Number options help

ensure a reliable, loop-free data link. – The Magic Number field helps in detecting links

that are in a looped-back condition. – Until the Magic-Number Configuration Option has

been successfully negotiated, the Magic-Number must be transmitted as zero.

– Magic numbers are generated randomly at each end of the connection.


• Multilink – Multilink PPP (also referred to as MP, MPPP, MLP,

or Multilink) provides a method for spreading traffic across multiple physical WAN links while providing packet fragmentation and reassembly, proper sequencing, multivendor interoperability, and load balancing on inbound and outbound traffic.


• PPP Callback – With this LCP option, a Cisco router can act as a

callback client or a callback server. – The client makes the initial call, requests that the

server call it back, and terminates its initial call. – The callback router answers the initial call and

makes the return call to the client based on its configuration statements.

PPP Configuration (1)

• Example 1: Enabling PPP on an Interface– To set PPP as the encapsulation method used by a

serial or ISDN interface, use the encapsulation ppp interface configuration command.

R3#configure terminalR3(config)#interface serial 0/0/0R3(config-if)#encapsulation ppp


• Example 2: Compression– You can configure point-to-point software

compression on serial interfaces after you have enabled PPP encapsulation.

– If the traffic already consists of compressed files (.zip, .tar, or .mpeg, for example), do not use this option

R3(config)#interface serial 0/0/0R3(config-if)#encapsulation pppR3(config-if)#compress [predictor | stac]


• Example 3: Link Quality Monitoring– In this phase, LCP tests the link to determine

whether the link quality is sufficient to use Layer 3 protocols.

– The percentages are calculated for both incoming and outgoing directions.

R3(config)#interface serial 0/0/0R3(config-if)#encapsulation pppR3(config-if)#ppp quality 80


• Example 4: Load Balancing Across Links (1)– Multilink PPP (also referred to as MP, MPPP, MLP, or

Multilink) provides a method for spreading traffic across multiple physical WAN links while providing packet fragmentation and reassembly, proper sequencing, multivendor interoperability, and load balancing on inbound and outbound traffic.


• Example 4: Load Balancing Across Links (2)– MPPP allows packets to be fragmented and sends

these fragments simultaneously over multiple point-to-point links to the same remote address.

– The multiple physical links come up in response to a user-defined load threshold.

Router(config)#interface serial 0/0/0Router(config-if)#encapsulation pppRouter(config-if)#ppp multilink

Verify PPP configuration (1)

Verify PPP configuration (2)

Troubleshooting PPP (1)

Configuring PPP Authentication (1)

Frame Relay

W.lilakiatsakun

Introduction (1)

• Frame Relay is a high-performance WAN protocol that operates at the physical and Data Link layers of the OSI reference model. – a simpler version of the X.25 protocol

• Network providers commonly implement Frame Relay for voice and data as an encapsulation technique, used between LANs over a WAN.

Introduction (2)

Introduction (3)

Introduction (4)

Introduction (5)

Introduction to Frame Relay (1)

• Frame Relay has lower overhead than X.25 because it has fewer capabilities.– Frame Relay does not provide error correction,

modern WAN facilities offer more reliable connection services and a higher degree of reliability than older facilities.

– The Frame Relay node simply drops packets without notification when it detects errors.


• Frame Relay handles volume and speed efficiently by combining the necessary functions of the data link and Network layers into one simple protocol. – As a data link protocol, Frame Relay provides

access to a network, delimits and delivers frames in proper order, and recognizes transmission errors through a standard Cyclic Redundancy Check.


– As a network protocol, Frame Relay provides multiple logical connections over a single physical circuit and allows the network to route data over those connections to its intended destinations.

Frame Relay Operation (1)

• The connection between a DTE device and a DCE device consists of both a Physical layer component and a link layer component:– The physical component defines the mechanical,

electrical, functional, and procedural specifications for the connection between the devices.

Frame Relay Operation (2)

– The link layer component defines the protocol that establishes the connection between the DTE device, such as a router, and the DCE device, such as a switch.

• Frame Relay access device (FRAD) is known as the DTE.– The FRAD is sometimes referred to as a Frame

Relay assembler/dissembler and is a dedicated appliance or a router configured to support Frame Relay.

Virtual Circuit (1)

• The connection through a Frame Relay network between two DTEs is called a virtual circuit (VC). – The connection is logical, and data moves from

end to end, without a direct electrical circuit. – With VCs, Frame Relay shares the bandwidth

among multiple users

Virtual Circuit (2)

Virtual Circuit (3)

• There are two ways to establish VCs:– SVCs, switched virtual circuits, are established

dynamically by sending signaling messages to the network (CALL SETUP, DATA TRANSFER, IDLE, CALL TERMINATION).

– PVCs, permanent virtual circuits, are preconfigured by the carrier, and after they are set up, only operate in DATA TRANSFER and IDLE modes. • Note that some publications refer to PVCs as private

VCs.

Frame Relay DLCIs (1)

• Frame Relay DLCIs (Data Link Connection Identifier)– They have local significance, which means that the

values themselves are not unique in the Frame Relay WAN.

– A DLCI identifies a VC to the equipment at an endpoint.

– Two devices connected by a VC may use a different DLCI value to refer to the same connection.

Multiple VC (1)

• Frame Relay is statistically multiplexed, meaning that it transmits only one frame at a time, but that many logical connections can co-exist on a single physical line.– This capability often reduces the equipment and

network complexity required to connect multiple devices, making it a very cost-effective replacement for a mesh of access lines

Multiple VC (2)

Frame Relay Encapsulation (1)


• DLCI – The 10-bit DLCI is the essence of the Frame Relay

header. – This value represents the virtual connection

between the DTE device and the switch.– Each virtual connection that is multiplexed onto

the physical channel is represented by a unique DLCI.


• Extended Address (EA) – If the value of the EA field is 1, the current byte is

determined to be the last DLCI octet. – Although current Frame Relay implementations all

use a two-octet DLCI, this capability does allow longer DLCIs in the future.

– The eighth bit of each byte of the Address field indicates the EA.


• C/R (Command/Response)– The bit that follows the most significant DLCI byte

in the Address field. – The C/R bit is not currently defined.

• Congestion Control ( The FECN, BECN, and DE bits ) contains 3 bits that control the Frame Relay congestion-notification mechanisms.

Frame Relay Topology (1)

• Star Topology (Hub and Spoke)– A Company has a central site that acts as a hub and

hosts the primary services. • the location of the hub is usually chosen by the lowest

leased-line cost

– Connections to each of the remote sites act as spokes. • each remote site has an access link to the Frame Relay

cloud with a single VC.


• Full Mesh Topology– A full mesh topology suits a situation in which the

services to be accessed are geographically dispersed and highly reliable access to them is required.

– A full mesh topology connects every site to every other site.


• Partial Mesh Topology– With partial mesh, there are more

interconnections than required for a star arrangement, but not as many as for a full mesh.

– The actual pattern is dependant on the data flow requirements.

Frame Relay Address Mapping (1)

• Inverse ARP (The Inverse Address Resolution Protocol) – To obtain Layer 3 addresses of other stations from

Layer 2 addresses, such as the DLCI in Frame Relay networks.

– It is primarily used in Frame Relay and ATM networks.


• Dynamic Mapping– The Frame Relay router sends out Inverse ARP

requests on its PVC to discover the protocol address of the remote device.

– The router uses the responses to populate an address-to-DLCI mapping table on the Frame Relay router or access server.

Frame Relay Address Mapping (3)• Static Mapping – The user can choose to override dynamic Inverse

ARP mapping by supplying a manual static mapping for the next hop protocol address to a local DLCI.

– You cannot use Inverse ARP and a map statement for the same DLCI and protocol.

LMI (Local Management Interface) (1)

• The LMI is a keepalive mechanism that provides status information about Frame Relay connections between the router (DTE) and the Frame Relay switch (DCE). – Every 10 seconds or so, the end device polls the

network, either requesting a dumb sequenced response or channel status information.


– If the network does not respond with the requested information, the user device may consider the connection to be down.

– When the network responds with a FULL STATUS response, it includes status information about DLCIs that are allocated to that line.

– The end device can use this information to determine whether the logical connections are able to pass data.


• LMI Extensions (1)– VC status messages• Provide information about PVC integrity by

communicating and synchronizing between devices, periodically reporting the existence of new PVCs and the deletion of already existing PVCs. • VC status messages prevent data from being sent into

black holes (PVCs that no longer exist).


• LMI Extensions (2)– Multicasting • Allows a sender to transmit a single frame that is

delivered to multiple recipients. • Multicasting supports the efficient delivery of routing

protocol messages and address resolution procedures that are typically sent to many destinations simultaneously.


• LMI Extensions (3)– Global addressing • Gives connection identifiers global rather than local

significance, allowing them to be used to identify a specific interface to the Frame Relay network. • Global addressing makes the Frame Relay network

resemble a LAN in terms of addressing, and ARPs perform exactly as they do over a LAN.


• LMI Extensions (4)– Simple flow control• Provides for an XON/XOFF flow control mechanism that

applies to the entire Frame Relay interface. • It is intended for those devices whose higher layers cannot

use the congestion notification bits and need some level of flow control

LMI Frame Format

LMI Operation (1)

LMI Operation (2)

LMI Operation (3)

LMI Operation (4)

LMI Operation (5)

LMI Operation (6)

LMI Operation (7)

Configuring Basic Frame Relay (1)

Configuring Static Map (1)


• Broadcast Keyword– Frame Relay, ATM, and X.25 are nonbroadcast

multiaccess (NBMA) networks.– NBMA networks do not support multicast or

broadcast traffic, so a single packet cannot reach all destinations

– Some routing protocols may require additional configuration options. • For example, RIP, EIGRP and OSPF require additional

configurations to be supported on NBMA networks.


• Because NBMA does not support broadcast traffic, using the broadcast keyword is a simplified way to forward routing updates. The broadcast keyword allows broadcasts and multicasts over the PVC and, in effect, turns the broadcast into a unicast so that the other node gets the routing updates.

Advanced Frame Relay Concept (1)

• Split Horizon (1)– Recall that split horizon is a technique used to

prevent a routing loop in networks using distance vector routing protocols.

– Split horizon updates reduce routing loops by preventing a routing update received on one interface to be forwarded out the same interface.


• Split Horizon (2)• R1 has multiple PVCs on a single physical

interface, so the split horizon rule prevents R1 from forwarding that routing update through the same physical interface to other remote spoke routers (R3).


• To solving the problems, Frame Relay subinterfaces are used– A subinterface is simply a logical interface that is

directly associated with a physical interface. – A partially meshed network can be divided into a

number of smaller, fully meshed, point-to-point networks.


• Point-to-point subinterface – It establishes one PVC connection to another physical

interface or subinterface on a remote router. – In this case, each pair of the point-to-point routers is

on its own subnet, and each point-to-point subinterface has a single DLCI.

– Typically, there is a separate subnet for each point-to-point VC.

– Therefore, routing update traffic is not subject to the split horizon rule.


• Multipoint Subinterface– It establishes multiple PVC connections to multiple

physical interfaces or subinterfaces on remote routers.

– All the participating interfaces are in the same subnet.

– The subinterface acts like an NBMA Frame Relay interface, so routing update traffic is subject to the split horizon rule (not resolve split horizon issue).


• Access rate or port speed– From a customer's point of view, the service

provider provides a serial connection or access link to the Frame Relay network over a leased line.

– These are typically at 56 kb/s, T1 (1.536 Mb/s), or Fractional T1 (a multiple of 56 kb/s or 64 kb/s).

– Port speeds are clocked on the Frame Relay switch


• Committed Information Rate (CIR) – The CIR is the amount of data that the network

receives from the access circuit. – The service provider guarantees that the

customer can send data at the CIR. – All frames received at or below the CIR are

accepted.


• Oversubscription– Service providers sometimes sell more capacity

than they have on the assumption that not everyone will demand their entitled capacity all of the time.

– The sum of CIRs from multiple PVCs to a given location is higher than the port or access channel rate.

– This can cause traffic issues, such as congestion and dropped traffic.


• Bursting– A great advantage of Frame Relay is that any

network capacity that is being unused is made available or shared with all customers, usually at no extra charge.

– Frame Relay can allow customers to dynamically access this extra bandwidth and "burst" over their CIR for free.

– The Committed Burst Information Rate (CBIR)/ Excess Burst (BE)

Frame Relay Flow Control (1)

• Congestion-notification mechanisms are the Forward Explicit Congestion Notification (FECN) and the Backward Explicit Congestion Notification (BECN).


• They let the router know that there is congestion and that the router should stop transmission until the condition is reversed.– BECN is a direct notification. – FECN is an indirect one.


• The provider's Frame Relay switch applies the following logic rules to each incoming frame based on whether the CIR is exceeded:– If the incoming frame does not exceed the CIR,

the frame is passed.– If an incoming frame exceeds the CIR, it is marked

DE. – If an incoming frame exceeds the CIR plus the BE,

it is discarded.

Configuring Frame Relay Subinterface (1)

The following command creates a point-to-point subinterface for PVC 103 to R3 R1(config-if)#interface serial 0/0/0.103 point-to-point.


R1(config-subif)#frame-relay interface-dlci 103.

Verify Frame Relay Operation (1)

ppp (point to point protocol)

Documents

ppp component

ppp point

ppp frame structure

ppp configuration option

completeestablish ppp

network layer datagrams

appletalk control protocol

sna control protocol