CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home
CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home
CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Point-to-Point Serial Links (Leased Lines)<br />
- The 2 most popular data link (L2) protocols that are being used over point-to-point serial links:<br />
HDLC High-Level Data Link Control. It was derived from Synchronous Data Link Control<br />
(SDLC) created by IBM. The HDLC specification was not intended to encapsulate<br />
(or support) multiple network layer protocols across the same link. It does not include<br />
a Protocol Type field and hence unable to identify the encapsulated network layer<br />
packets. Vendors that support HDLC must define their own proprietary HDLC<br />
headers that contain the Protocol Type field to identify the network layer protocols.<br />
Due to this reason, HDLC implementations are proprietary – <strong>Cisco</strong> routers will not<br />
work in connections to other vendor routers. It is the default encapsulation type used<br />
on <strong>Cisco</strong> synchronous serial interfaces. HDLC does not support error recovery.<br />
PPP Point-to-Point Protocol. It is an industry-standard protocol that provides an open<br />
standard for creating point-to-point links between different vendor equipments.<br />
It uses a standardized Protocol Type field – Network Control Protocol (NCP) field in<br />
the header to identify the encapsulated network layer packets. It supports<br />
authentication, multilink connections, and can operates over synchronous and<br />
asynchronous links. PPP uses HDLC to encapsulate and transmit packets over pointto-point<br />
links. PPP supports error recovery but is disabled by default.<br />
Note: HDLC was developed by the International Organization for Standardization (ISO).<br />
- HDLC does not need the arbitration feature as in Ethernet. Because on point-to-point serial links,<br />
routers can send over the 4 wires (2 twisted-pair wires) circuit at any time, and the signal<br />
(eventually data) will arrived at the other end of the link.<br />
- Both HDLC and PPP frames include an address field, but it is not being used and not really<br />
needed over point-to-point links.<br />
- Do not confuse error detection with error recovery! Almost all data link layer protocols including<br />
HDLC and PPP perform error detection with the FCS field in their trailers. Frames that fail the<br />
FCS check will be noticed and discarded (error detection). Error recovery is normally being<br />
performed by higher-layer protocols, eg: TCP.<br />
Point-to-Point Protocol (PPP)<br />
- When PPP was being developed, it includes many additional features that never been seen in<br />
other WAN data link protocols up to that time.<br />
- The PPP specification includes the following 2 subprotocols or sublayers:<br />
i) Link Control Protocol (LCP). Responsible for establishing, configuring, testing,<br />
maintaining, and terminating PPP connections. PPP was designed to work with several<br />
network layer protocols, hence each PPP link has a LCP and a NCP for the corresponding<br />
L3 protocol encapsulated and transmitted over the PPP link.<br />
ii) Network Control Protocols (NCPs). Responsible for encapsulating network layer<br />
protocols and assigning network layer addresses to the remote end over PPP links after<br />
the link establishment and authentication phases. The negotiated network layer protocols<br />
can then be transmitted across the PPP connection.<br />
Ex: IP Control Protocol (IPCP) for IP, IPX Control Protocol (IPXCP) for IPX, and<br />
AppleTalk Control Protocol (ATCP) for AppleTalk. A router configured for PPP<br />
encapsulation will try to identify the network layer protocol and use the appropriate<br />
network control protocol for the corresponding L3 protocol transmitted over the PPP link.<br />
150<br />
Copyright © 2008 Yap Chin Hoong<br />
yapchinhoong@hotmail.com