Remote Access For Cisco Network / Edition 11

Remote Access For Cisco Network / Edition 11

ISBN-10:
0071352007
ISBN-13:
9780071352000
Pub. Date:
08/01/1999
Publisher:
McGraw-Hill Companies, The
ISBN-10:
0071352007
ISBN-13:
9780071352000
Pub. Date:
08/01/1999
Publisher:
McGraw-Hill Companies, The
Remote Access For Cisco Network / Edition 11

Remote Access For Cisco Network / Edition 11

Paperback

$60.95
Current price is , Original price is $60.95. You
$60.95 
  • SHIP THIS ITEM
    Temporarily Out of Stock Online
  • PICK UP IN STORE

    Your local store may have stock of this item.


Overview

Build your remote connectivity know-how The ability to connect remotely through a Cisco Network is changing the way networking professionals do their jobs. Remote Access for Cisco Networks,by Bill Burton,CCIE,is the first complete guide to using Cisco networks remotely,from hardware to the IOS. It's a practical hands-on tool with troubleshooting tips and techniques in every chapter.

It's invaluable,too,for mastering the skill required in the CCIE Lab Exam and CCNP exam. You get a full understanding of routing protocol interactions,distance vector,and advanced protocols. Plus. . . directions for configuring asynchronous modems with Cisco routers. . . establishing backup circuits for permanent connections. . . and optimizing traffic flow on WAN interfaces

*insight into security and remote connectivity with PPP (Point to Point Protocol)

The complete guide to designing,implementing,and monitoring remote access systems in Cisco® networks!

Remote connectivity is a central component in the Cisco internetworking operating system (IOS) and router hardware. This important capability is drastically changing the way network professionals do their jobs,and it's also an important part of the CCIE™ Certification Exam. If you need to get up and running with this technology,then this book is for you. It provides all the essential information for understanding and implementing remote connectivity—invaluable information that the Cisco documentation just doesn't cover.

Coverage includes: Remote connectivity with all the permanent access connections (frame relay,X. 25 connections,and back-up connections)

Bandwidth on demand Troubleshooting tipsand techniques throughout every chapter Cisco lab objectives for developing remote access skills to pass the CCIE exam and meet certification requirements All network administrators and anyone who needs to learn about remote connectivity to pass the CCIE exam will find this to be their one-stop source for mastering this explosive technology.


Product Details

ISBN-13: 9780071352000
Publisher: McGraw-Hill Companies, The
Publication date: 08/01/1999
Series: McGraw-Hill Technical Expert Series
Pages: 516
Product dimensions: 1.04(w) x 7.50(h) x 9.25(d)

Read an Excerpt

Chapter 1: Asynchronous Terminal Services

Introduction

So we start. This first chapter will give you a brief technical overview of standard asynchronous communications. Then we will examine the basic terminal services provided by Cisco routers and access servers. The labs are simple to set up and can be accomplished with any Cisco router with an auxiliary port, asynchronous/synchronous port, or asynchronous communications port. Samples of all three are shown by the end of the chapter.

Asynchronous Communication

How do asynchronous communications work? After we answer this question, some of the commands we use on Cisco routers and access servers will make a little more sense.

Asynchronous data is transmitted in a serial manner, one bit at a time. If we just sent some random bits of information, it would be difficult to receive these random bits and make sense out of them. So in asynchronous communications, we organize the transmission of data in characters.

The beginning and end of each character of data must be identified by start and stop bits. The start bit indicates when the data byte is about to begin, and the stop bit signals when it ends. The requirement to send these additional two bits causes asynchronous communications to be slightly slower than synchronous; however, it has the advantage that the processor does not have to deal with the additional idle characters.

An asynchronous line that is idle is identified with a value of 1 (also called a mark state). By using this value to indicate that no data is currently being sent, the devices are able to distinguish between an idle state and a disconnected line. When a character is about to betransmitted, a start bit is sent. A start bit has a value of 0 (also called a space state). Thus when the line switches from a value of 1 to a value of 0, the receiver is alerted that a data character is about to come down the line.

Once the start bit has been sent, the transmitter sends the actual data bits. There may either be five, six, seven, or eight data bits, depending on the number you have selected. Both the receiver and the transmitter must agree on the number of data bits, parity, and the baud rate (see below). Almost all devices transmit data using either seven or eight data bits. Note that when only seven data bits are employed, you cannot send ASCII values greater than 127. After the data has been transmitted, a stop bit is sent. A stop bit has the value of 1 (mark state) and is 1, 1.5, or 2 bits long and can be detected correctly even if the previous data bit also had a value of 1. Character termination is accomplished by the stop bit's duration; this forces a mark state (idle) between characters.

Besides the synchronization provided by the use of start and stop bits, an additional bit called a parity bit may optionally be transmitted along with the data. A parity bit affords a small amount of error checking, to help detect data corruption that might occur during transmission. You can choose: even parity, odd parity, mark parity, space parity, or none at all. When even or odd parity is being used, the number of marks (logical 1 bits) in each data byte are counted, and a single bit is transmitted following the data bits to indicate whether the number of 1 bits just sent is even or odd. For example, when even parity is chosen, the parity bit is transmitted with a value of 0 if the number of preceding marks is an even number. For the eight-bit binary value of 0110 0 011, the parity bit would be 0. If even parity were in effect and the binary number 1101 0110 were sent, then the parity bit would be 1. Odd parity is just the opposite, and the parity bit is 0 when the number of mark bits in the preceding word is an odd number. The parity rule is simple: for even parity, the number of mark bits must be even; for odd parity, the number of mark bits must be odd. The parity bit is either a mark or space to make the parity correct. Parity error checking is very basic, and while it will tell you if there is a single bit error in the character, it doesn't show which bit was received in error. If an even number of bits are in error, then the parity bit would not reflect any error at all. Mark parity means that the parity bit is always set to the mark signal condition, and the space parity always sends the parity bit in the space signal condition. Since these two parity options serve no useful purpose whatsoever, they are almost never used. Figure 1-1 shows some sample character transmissions.

FYI The common shorthand for defining data stream characteristics is 8-N-1. First comes the number of data bits: 5, 6, 7, or 8. Second is parity: N(one), E(ven), O(dd), S(pace), or M(ark). Third is the number of stop bits: 1, 1.5, or 2.

Sample #1 illustrates a sample bit stream of 1100 1001 if the definition we use is eight data bits, no parity, and one stop bit, or 8-N-1. At sample time 1, the line is idle or in the mark state (1). When the line state changes to a space state (0), the line detects the start bit and sets up a sampling rate based on the bits per second defined. When the next sample time comes, the line starts clocking in bits by sampling the data stream level for is and Os. The stop bit(s) at the end of the character stream forces the data stream to a mark or idle condition so that the data stream will correctly identify the start of a new character with a space start bit.

QUESTION #1 Based on the following data stream definitions for samples #2, #3, and #4, what are the characters being transmitted in binary, and are they valid characters or not? You will find answers to these questions at the end of the chapter.

Sample #2's definition is 5-E-1 Sample #3's definition is 8-E-2 Sample #4's definition is 7-0-1.

Transmission speed is the one area that has not been discussed. Transmission speed is based on a clocking signal. When we get to cabling and physical layer signalling in Appendix A, we will see that there is no clocking signal between the two end points. How does the circuitry at each end know how fast to send the data stream? Each end must set matching speeds in bits per second to transmit and receive data correctly. There is another option when it comes to setting up the transmission speed at either end. The feature is referred to as autobaud. If there is a known character being received, and the speed is correct, then the character will be properly decoded. This only works if the bits per character and parity are correctly defined. Autobaud works by starting with the maximum speed available on the port or line, and checking to see if the known character is received. If the transmission is not decoded correctly, then the initial speed is reduced to the next lower standard speed, and the data stream is checked again. This process is repeated until the correct speed is detected...

Table of Contents

Preface xi
Acknowledgments xvii
Asynchronous Terminal Services
1(40)
Introduction
2(1)
Asynchronous Communication
2(4)
Configuring Dial Access
6(8)
HyperTerminal Setup
14(5)
Modem Setup
19(20)
Automatic Configuration
20(5)
Chat Scripts
25(14)
Summary
39(1)
Questions and Answers
40(1)
Advanced Terminal Services
41(28)
Virtual Terminal Sessions
42(6)
Menus
48(5)
Autocommand Process
53(6)
Access-Class
59(4)
System Controllers
63(5)
Summary
68(1)
Point-to-Point Protocol
69(12)
Physical Layer
70(1)
Link Control Protocol (LCP)
71(4)
Authentication
75(2)
Network Control Protocol (NCP)
77(3)
IP Control Protocol (IPCP)
77(1)
Apple Talk Control Protocol (ATCP)
78(1)
IPX Control Protocol (IPXCP)
79(1)
Multilink PPP
80(1)
Summary
80(1)
IP Dial Access
81(38)
Windows 95/98 Dial-In Setup
82(7)
Programming the Cisco Router/Access Server
89(11)
PPP Multilink
100(17)
Troubleshooting Techniques
117(1)
Summary
117(2)
Dial-on-Demand Routing
119(34)
Routing
120(1)
Interesting Traffic
121(1)
Address Resolution
122(7)
Authentication
129(1)
Putting It All Together
129(22)
Troubleshooting Techniques
151(1)
Lab
151(1)
Summary
152(1)
Integrated Services Digital Network
153(66)
One-to-One Basic Connectivity Using Static Routes
156(15)
One-to Many Basic Connectivity Using Static Routes
171(17)
Basic BRI-to-PRI Connectivity
188(8)
Dialer Profiles
196(20)
Dialer Profile Sidebar
206(10)
Summary
216(1)
Questions and Answers
217(2)
DDR with IP Routing Protocols
219(52)
Route Redistribution for Multiple Dial-in Connections
220(12)
London
221(3)
NewYork
224(2)
Rome
226(3)
SOHO800
229(3)
Snapshot Routing for Distance Vector Protocols
232(14)
London
233(4)
NewYork
237(2)
Rome
239(4)
SOHO800
243(3)
OSPF Dial-in Connectivity
246(14)
London
246(3)
NewYork
249(4)
Rome
253(2)
Paris
255(5)
On-Demand Routing with EIGRP
260(9)
London
260(4)
NewYork
264(3)
SOHO800
267(2)
Summary
269(2)
The AS5200 High-end Access Server
271(20)
Basics
272(17)
SOHO700
273(5)
London
278(3)
NewYork
281(8)
Summary
289(2)
Fixed-facility WAN Services
291(42)
High-level Data Link Control (HDLC)
292(5)
NewYork
292(4)
London
296(1)
Channelized TI
297(4)
London
297(2)
NewYork
299(2)
X.25 Packet Services
301(8)
X25 Switch
302(3)
London
305(2)
NewYork
307(2)
Frame Relay Services
309(22)
Multipoint Frame Relay with Static Mapping
310(1)
Rome
311(2)
London
313(1)
Seoul
314(1)
NewYork
315(1)
Multipoint Frame Relay with Inverse ARP
316(1)
Rome
316(3)
London
319(1)
Seoul
320(1)
NewYork
321(1)
Point-to-Point Frame Relay Using Subinterfaces
322(1)
Rome
323(1)
London
324(3)
Seoul
327(1)
NewYork
328(3)
Summary
331(2)
Backing Up Fixed WAN Connections
333(16)
Backup Interface Command
334(1)
Floating Static Routes
334(1)
Dialer Watch
335(1)
Making it work
335(12)
London
335(6)
Tokyo
341(3)
NewYork
344(3)
LAB Challenge
347(1)
Summary
347(2)
Advanced Security with TACACS+ and RADIUS
349(34)
TACACS+
350(1)
Radius
350(1)
CiscoSecure ACS v2.1 for NT
351(5)
AAA Operating Commands
356(21)
Authentication
356(4)
Authorization
360(1)
Accounting
361(4)
London
365(2)
NewYork
367(10)
Exec-Level Testing
377(4)
Summary
381(2)
Protocol Translation
383(12)
X.25 Switch
385(1)
London
386(1)
NewYork
387(3)
Paris
390(4)
Summary
394(1)
Network Address Translation
395(16)
Summary
409(2)
Troubleshooting
411(14)
Physical Layer
412(1)
Asynchronous Connections
412(1)
ISDN BRI Connections
412(1)
Synchronous Connections
413(1)
Data-link Layer
413(2)
HDLC Connections
413(1)
PPP Connections
413(1)
ISDN BRI Connections
414(1)
ISDN PRI Connections
415(1)
X.25 Connections
415(1)
Frame Relay Connections
415(1)
Network Layer
415(1)
X.25 Connections
415(1)
ISDN Connections
416(1)
PPP Connections
416(1)
Dial-on-Demand Routing (DDR)
416(7)
Summary
423(2)
Appendix A EIA/TIA-232 Physical Specifications 425(2)
Appendix B AT Modem Commands 427(2)
Appendix C RFC List and Other Reference Material 429(4)
Appendix D ISDN SPID Guidelines 433(4)
Appendix E ISDN Q921 Debugging 437(12)
Appendix F The Frame Relay Switch Configuration 449(6)
Appendix G CiscoSecure Reports 455(4)
Appendix H 459(2)
Glossary 461(22)
Index 483
From the B&N Reads Blog

Customer Reviews