| Home Page | Company Profile | Capabilities | Coming Events | Case Studies | White Papers | Book
Copyright 1999-2001 © Networking Unlimited Inc.
All rights reserved.
High Availability Networking
with Cisco
Vincent C. Jones
Page 143, Last two paragraphs (& following) Posted 23 April 2001. Thanks to Alex Zinin.
The limitation on dialer watch that required the use of IGRP or EIGRP for the routing protocol no longer exists. Use of dialer watch with OSPF and other routing protocols is fully supported in the GD release of IOS 12.0 (and in subsequent IOS releases).
This correction also applies to page 145 (second to last paragraph), page 169 (first paragraph), page 216 (third paragraph), page 263 (first paragraph), page 264 (first two paragraphs), page 266 (third paragraph), and page 268 (2nd paragraph, 1st bullet).
Page 145, Second to last paragraph Posted 23 April 2001. Thanks to Alex Zinin.
See page 143 regarding dialer watch restriction update.
Page 155, Listing 4-5. Posted 25 February 2001. Thanks to Juergen Braendle.
The line "ip host CallISDN 10.0.0.6" should read "ip host CallISDN 10.0.0.129." The copy of Listing 4-5 posted on this web site was revised 25 February 2001.
Page 162, last line on the page. Posted 25 February 2001. Thanks to Juergen Braendle.
The IP address "10.0.0.6" should read "10.0.0.129."
Page 163 & page 164, Listing 4-7. Posted 25 February 2001. Thanks to Juergen Braendle.
The line "ip host CallISDN 10.0.0.6" should read "ip host CallISDN 10.0.0.129" on page 163. The line "ip route 0.0.0.0 0.0.0.0 10.0.0.6 150" should read "ip route 0.0.0.0 0.0.0.0 10.0.0.129 150" on page 164. The copy of Listing 4-7 posted on this web site was revised 25 February 2001.
Page 169, First paragraph Posted 23 April 2001. Thanks to Alex Zinin.
See page 143 regarding dialer watch restriction update.
Page 177, Listing 5-1. Posted 25 February 2001. Thanks to Aaron Leonard.
Using "script reset" and "script startup" for the purpose of keeping modems properly configured can be problematic. Cisco has had some significant problems with reset chat scripts thru the years, including:
CSCdi29975 stack overflow when using the line reset chat script (fixed in 10.3(3))
CSCdi78178 Modem reset script wont run after PPP or SLIP sessions (11.2(6))
CSCdp19980 Modem chat reset script not working in PPP mode (12.1(3))
CSCdr51056 reset chat scripts run at the wrong times (12.1(5))
CSCds18377 reset chat scripts do not reset connected modems (still broken as of February 2001)
So, in general, reset chat scripts should be avoided. Modem autoconfigure type (introduced in IOS 11.1) is a much more robust and flexible method. See Task 2 in the Modem Management Operations chapter of Cisco's "AS5x00 Case Study for Basic IP Modem Services" for more specific guidelines. (Available at:
http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/as5xipmo/mostats.htm#xtocid235605
). If using "modem autoconfigure" you must NOT use "script reset." The two approaches should be considered mutually exclusive.
The copy of Listing 5-1 posted on this web site was revised 25 February 2001. This suggestion also applies to Listings 5-12, 6-19, 6-23 and 6-24 (and web-site-only Listing 6-24d), all of which were revised 25 February 2001.
Page 216, Third paragraph Posted 23 April 2001. Thanks to Alex Zinin.
See page 143 regarding dialer watch restriction update.
Page 247, first paragraph. Posted 25 February 2001. Thanks to Mitchell Shnier.
Many DHCP implementations, including versions of Microsoft Windows, will remember DHCP leases across a reboot or power cycle. For these systems, implementation specific commands must be used to clear existing DHCP leases.
Page 263, First paragraph Posted 23 April 2001. Thanks to Alex Zinin.
See page 143 regarding dialer watch restriction update.
Page 264, First two paragraphs Posted 23 April 2001. Thanks to Alex Zinin.
See page 143 regarding dialer watch restriction update.
Page 266, Third paragraph Posted 23 April 2001. Thanks to Alex Zinin.
See page 143 regarding dialer watch restriction update.
Page 268, Second paragraph, first bullet Posted 23 April 2001. Thanks to Alex Zinin.
See page 143 regarding dialer watch restriction update.
Page 277, Listing 5-12. Posted 25 February 2001.
See entry for Page 177, Listing 5-1. The copy of Listing 5-12 posted on this web site was revised 25 February 2001.
Page 284, Listing 6-19. Posted 25 February 2001.
See entry for Page 177, Listing 5-1. The copy of Listing 6-19 posted on this web site was revised 25 February 2001.
Page 303, Listing 6-23. Posted 25 February 2001.
See entry for Page 177, Listing 5-1. The copy of Listing 6-23 posted on this web site was revised 25 February 2001.
Page 307, Listing 6-24. Posted 25 February 2001.
See entry for Page 177, Listing 5-1. The copy of Listing 6-24 posted on this web site was revised 25 February 2001.
Page 179, Table 5-1, Posted 25 February 2001. Thanks to Mitchell Shnier.
One of my favorite modem commands to add is S11=50, to decrease the time the modem sends (in milliseconds) each DTMF tone (and the silent time between tones). This can save a valuable second or two of call set-up time. Also, the speaker might need to be louder (L2 rather than L1) if the modem is in a noisy computer room.
Page 56, middle of the page. Posted 25 February 2001.
The maximum diameter of a 10base5 network can theoretically be up to 2800m (rather than 2500m) if you count the transceiver cables.
Page 66, Figure 2.14. Posted 25 February 2001.
There are two links shown connecting to the left-most user workstation on the 4th floor. This could be considered a typo or an unmentioned dual-homed user.
Page 73, second paragraph. Posted 25 February 2001.
The 180 and 120 second timers are six and four update intervals, not three and two update intervals.
Page 162, Figure 4-3. Posted 23 April 2001.
The caption should read "Figure 4-3. Dial-on-demand backup for a DSL link."
Page 180, near top of page. Posted 25 February 2001.
Should say MNP4, not MMP4.
Page 236, Note 1. Posted 25 February 2001.
"Hexidecimal" should read "hexadecimal."
Page 395, last line on the page. Posted 25 February 2001.
The Cisco command "no ip route ??due?" should read "no ip route-cache."
Page 397, Listing 8-11. Posted 25 February 2001.
The line at the top of the page "isdu caller 2125551212" should read "isdn caller 2125551212." The listing posted on this web site is correct.
Page 452, Listing 8-28. Posted 23 April 2001. Updated 3 July 2001. Thanks to Hal Snyder.
The line "default-information originate" under "router bgp 60000" is not
needed, but does no harm being present.
The copy of Listing 8-28 posted on this web site was revised 3 July 2001.
The caption should read "Listing 8-28. Router External #1 speaking EBGP to one ISP and IBGP to router External #2."
Page 454, Listing 8-29. Posted 3 July 2001. Thanks to Hal Snyder.
Add the line "ip address 120.0.0.1 255.255.255.252" under "interface Serial2/0."
The line "default-information originate" under "router bgp 60000" is not
needed, but does no harm being present.
The copy of Listing 8-29 posted on this web site was revised 3 July 2001.
| Home Page | Company Profile | Capabilities | Coming Events | Case Studies | White Papers | Book
Copyright 1999-2001 © Networking Unlimited Inc.
All rights reserved.