Tài liệu AppleTalk Lab Scenario One ppt

CertificationZone Page 1 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
Date of Issue: 10-01-1999
AppleTalk Lab Scenario One
Troubleshooting Basic AppleTalk
Configuration
by Priscilla Oppenheimer
Introduction
In this scenario, you will be asked to troubleshoot the AppleTalk internetwork shown in Figure 1.
Figure 1
Lab Scenario One:
Troubleshooting Basic AppleTalk
Configuration
Introduction
Equipment Required
Scenario Background
Success Criteria
Procedure
Initial Configurations
Passwords
Tips and Debriefing
Configuration Bugs Revealed
Monroe
Bogart
Gable
Fonda
Lab Scenario Two:
Troubleshooting Enhanced IGRP for AppleTalk
Introduction
Equipment Required
Scenario Background

Success Criteria
Procedure
Configuration Updates
Passwords
Tips and Debriefing
Configuration Bugs Revealed
Bogart
Monroe
Gable
Fonda
CertificationZone Page 2 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
The configurations for each of the routers are provided, but they have some bugs. You have three options:
1. Use your own configurations and get the internetwork up and running without benefit of the provided configurations.
2. Troubleshoot the provided configurations before you download them to the routers.
3. Download the provided configurations and then use Cisco IOS show and debug commands to isolate the problems.
Remove and add configuration commands to get the internetwork up and running.
Option 3 is the recommended approach because it closely resembles the second day of the CCIE lab test. On the
second day of the test, the lab proctor will break your existing configurations, or provide new buggy configurations,
and ask you to troubleshoot the problems.
Equipment Required
To complete this lab scenario, you will need the following equipment:
• One router with two serial ports
• Two routers that each have one serial port and one Ethernet port
• One router that has an Ethernet port and a Token Ring port
• A Token Ring multistation access unit (MAU)
• A Token Ring cable to connect the Token Ring router
• Ethernet cabling and optionally two Ethernet hubs
• Two cross-over serial cables
• A personal computer

• A console cable to connect the serial port of the personal computer to the console port of a router
• Terminal software for the personal computer, such as HyperTerminal
• Optional: Telnet software for the personal computer
If you don't have all of this equipment, you can modify the lab scenario and router configurations to match the
equipment you do have.
Scenario Background
In this scenario, the Monroe router is at company headquarters. The Monroe router connects to two remote offices via
serial links. The Manufacturing remote office has a single router, named Fonda, that connects to an Ethernet LAN.
The other remote office has two routers, Bogart and Gable. This remote office has an Ethernet and a Token Ring LAN
which are used by marketing, sales, and administrative staff.
The company currently uses the Routing Table Maintenance Protocol (RTMP) for AppleTalk routing. Recently a junior
engineer took on the job of reducing routing traffic on the serial link between headquarters and the
Marketing/Sales/Administration remote office. He made a few attempts to reduce traffic, but his changes have caused
problems for the entire internetwork. While troubleshooting the problems, he introduced a few additional bugs
unrelated to reducing traffic on the serial link.
Because you are a senior network engineer, you have been given the job of getting this internetwork up and running
again. You are aware that the future plan is to migrate to Enhanced IGRP for AppleTalk, so for now you can remove
the junior engineer's attempts to reduce routing traffic. (AppleTalk Scenario Two deals with the upgrade to Enhanced
IGRP.)
CertificationZone Page 3 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
Although not essential to this lab scenario, all routers are also configured for IP with Enhanced IGRP as the routing
protocol. This will facilitate your using Telnet to reach the routers and IP ping to troubleshoot basic connectivity.
However, keep in mind that your goal is to get the AppleTalk internetwork running. Don't assume that the AppleTalk
internetwork is working just because IP is working. The junior engineer has not touched the IP configuration. IP
should work correctly. You should concentrate on troubleshooting AppleTalk.
Success Criteria
You will know that the AppleTalk internetwork is up and running again when each router can see the following five
networks:
The zone list should look like this:

If you see fewer networks and zones, or if you see more networks and zones than what is listed above, then you have
not completed the lab. Also, the network numbers and zone names must exactly match the ones shown. To help you
understand the success criteria, you can look at the results of a show appletalk route and a show appletalk zone
for correctly-configured routers by clicking on the following links:
• Monroe
• Bogart
• Gable
• Fonda
In addition to using the show appletalk route and show appletalk zone commands to verify configuration, you must
also be able to ping each interface of each router with an AppleTalk ping command.
Procedure
As mentioned in the Introduction, the best method to use if you want to emulate the CCIE test is to download the
provided configurations and then use show and debug commands to troubleshoot the problems. Don't examine the
configurations first. Just download them. If you prefer, you can develop your own configurations based on the network
drawing in Figure 1. Or, you can study the provided configurations before downloading them and attempt to fix the
configurations before using them.
Network Zone(s)
Net 10-10 zzzserial
Net 20-20 zzzserial
Net 30-30 MarketingAndSales
Net 40-40 Admin
Net 50-50
VirtualTeams
Additional zone for net 50-50: Manufacturing
Name Network(s)
Admin 40-40
MarketingAndSales 30-30
zzzserial 20-20 10-10
VirtualTeams 50-50
Manufacturing 50-50

Note:
These links should open in new
browser windows. You can open
several at a time and switch
between them. Simply close the
window(s) to return to this
document.
CertificationZone Page 4 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
This procedure assumes you will use the option of downloading the provided configurations and then troubleshooting
them.
1. Erase the startup configuration on each router.
2. Reboot each router.
3. Do not go into setup mode.
4. On each router, go into enable mode and then configuration mode.
5. Open the configuration file for a router and select all text and copy the text to the clipboard.
6. In your terminal window, paste the commands you copied in the previous step into the appropriate router's
configuration.
7. Repeat steps 5 and 6 for each remaining router.
8. Troubleshoot the problems, and remove and add commands until you have met the success criteria.
Initial Configurations
Each router's initial configuration can be accessed by clicking on the following links:
• Monroe
• Bogart
• Gable
• Fonda
Passwords
The configuration files do not have any passwords assigned to the console or VTY lines. There is an enable password
assigned. The enable password is cisco. There is no enable secret password.
Tips and Debriefing

Do not read this section until you have worked on the lab and have either met the success criteria or have decided
you need some hints.
When troubleshooting, a few tips to keep in mind are as follows:
• To isolate possible port-configuration-mismatch problems or problems with ports staying stuck in acquiring mode,
use the show appletalk interface and debug appletalk events commands.
• When making changes to cable ranges and zones, shut down the relevant interfaces first. Make the changes and
then leave the interfaces shut for a minute or two. This gives the routers time to flush bad entries in the routing and
zone tables.
Be sure to have a console cable and terminal software handy when troubleshooting. Because you may shut down
interfaces while troubleshooting, you might not be able to reach all the routers via Telnet.
As you should know by now, each router configuration has minor bugs and anomalies. To see a list of the bugs, read
Configuration Bugs Revealed.
If you give up, or if you want to verify your completed work, you can view the correct configurations for each router
here:
Note:
These links should open in new
browser windows. You can open
several at a time and switch
between them. Simply close the
window(s) to return to this
document.
CertificationZone Page 5 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
• Monroe
• Bogart
• Gable
• Fonda
Configuration Bugs Revealed
Do not read further until you have attempted to solve the problems! This is the explanation of the bugs that were
inserted into each router's configuration.

Monroe
• On the Monroe router the command no appletalk send-rtmps is configured on the S1 interface. This command
causes the S0 port on Bogart not to initialize. The SO port on Bogart remains stuck in a state of "acquiring port net
info" until you remove the no appletalk send-rtmps command on Monroe. You can use the show appletalk
interface S0 command on Bogart to identify the problem. (Note: if Bogart's SO port had also been configured for no
appletalk send-rtmps then it would not have gotten stuck. However, without RTMPs, you would need many static
routes, or Enhanced IGRP for AppleTalk or AURP.)
• On Monroe's S1 port a static AppleTalk address is used. The command appletalk cable-range 10-10 10.104 states
that Monroe should always use node ID 10.104 on S1. This is not a problem, but it is also not necessary once you
remove the uncalled-for static route in Bogart's configuration.
• On Monroe's S1 port, the zone is specified as ZZZSerial instead of zzzserial. This is not a problem. It is a "red
herring" (false clue). Zone names are case-insensitive.
• Monroe has access list 600 defined. This is also a red herring. The access list is not applied to any interface and
has no effect.
Bogart
• Bogart has the following unnecessary static route defined: appletalk static cable-range 50-50 to 10.104 zone
Virtual Teams. This static route was an attempt by the junior engineer to reduce traffic on the serial link. Since the
company will be migrating to Enhanced IGRP in the near future, the static route is not necessary.
• Not only is the static route not called for, but it has a bug. The zones associated with network 50-50 should be
VirtualTeams and Manufacturing. Note that VirtualTeams does not have a space in it. The correct commands to use,
if a static route was really a good idea, would have been:
appletalk static cable-range 50-50 to 10.104 zone VirtualTeams
appletalk static cable-range 50-50 to 10.104 zone Manufacturing
Gable
• Gable has the wrong zone name configured for its Ethernet network. The zone name does not match the zone name
configured on Bogart's E0 interface. The zone name should be MarketingAndSales, not Marketing AndSales. This
problem will cause Gable or Bogart to display a "port configuration mismatch" message when you enter the show
appletalk interface E0 command. (Which router displays the message depends on which router boots first.)
• On Gable's Token Ring interface, the cable range is incorrectly configured as 20-20. It should be 40-40. The cable
range 20-20 is already in use on the serial link between headquarters and the Manufacturing remote office.

Note:
These links should open in new
browser windows. You can open
several at a time and switch
between them. Simply close the
window(s) to return to this
document.
CertificationZone Page 6 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
Fonda
• On Fonda the appletalk routing command is missing. This means that none of the AppleTalk interface commands
ended up in the configuration, even though they are in the configuration file.
[IE-ApTk-LS1-F03]
[1999090801]
AppleTalk Lab Scenario Two
Troubleshooting Enhanced IGRP for
AppleTalk
by Priscilla Oppenheimer
Introduction
In this scenario, you will be asked to implement and troubleshoot the AppleTalk internetwork shown in Figure 1.
Figure 1
This scenario assumes you have completed CCIE AppleTalk Lab Scenario One. The customer has now asked you to
upgrade the internetwork to reduce traffic caused by the Routing Table Maintenance Protocol (RTMP). Configuration
updates for each of the routers are provided, but they have some bugs. You have three options:
1. Use your own configurations and get the internetwork up and running without benefit of the provided configurations.
2. Troubleshoot the provided configuration updates before you download them to the routers.
CertificationZone Page 7 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
3. Download the provided configuration updates and then use Cisco IOS show and debug commands to isolate the
problems. Remove and add configuration commands to make the internetwork operational.

Option 3 closely resembles the second day of the CCIE lab test. On the second day of the test, the lab proctor will
break your existing configurations, or provide new buggy configurations, and ask you to troubleshoot the problems.
Equipment Required
To complete this lab scenario, you will need the following equipment:
• One router with two serial ports
• Two routers that each have one serial port and one Ethernet port
• One router that has an Ethernet port and a Token Ring port
• A Token Ring multistation access unit (MAU)
• A Token Ring cable to connect the Token Ring router
• Ethernet cabling and optionally two Ethernet hubs
• Two cross-over serial cables
• A personal computer
• A console cable to connect the serial port of the personal computer to the console port of a router
• Terminal software for the personal computer, such as HyperTerminal
• Optional: Telnet software for the personal computer.
If you don't have all of this equipment, you can modify the lab scenario and router configurations to match the
equipment you do have.
Scenario Background
The physical topology for this scenario is the same as it was for Scenario One. The Monroe router is at company
headquarters. The Monroe router connects to two remote offices via serial links. The Manufacturing remote office has
a single router, named Fonda, that connects to an Ethernet LAN. The other remote office has two routers, Bogart and
Gable. This remote office has an Ethernet and a Token Ring LAN, which are used by marketing, sales, and
administrative staff.
In AppleTalk Scenario One, you made sure that the AppleTalk RTMP network was operational and that all cable
ranges and zones appeared in the routing and zone tables of all routers. In this scenario, you will be asked to migrate
from RTMP to Enhanced IGRP for AppleTalk.
Your boss, who is convinced he is a technical god, has written the configuration updates for each router and wants
you to download them to each router. He says that his updates will successfully upgrade the network, and that he has
correctly implemented the following policies that have been agreed upon in numerous network planning meetings:
• To reduce routing traffic on the serial links, no RTMP packets should be sent out any serial ports on any router.

• The Monroe router should run Enhanced IGRP only. It will not support RTMP.
• The Bogart router should run Enhanced IGRP on its serial link and RTMP on its Ethernet link.
• The Fonda router should run Enhanced IGRP on its serial link and RTMP on its Ethernet link.
• The Gable router should run RTMP only, and, on its Token Ring interface, it should be configured as a stub router.
CertificationZone Page 8 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
Stub configuration will work because there are no other routers on the Token Ring LAN, and there are no plans to
ever place any routers on the Token Ring LAN.
• All LAN users should be able to reach all LAN zones. However, to reduce NBP traffic on the serial links, the LAN
routers should be configured to not propagate the zzzserial zone.
Although not essential to this lab scenario, all routers are also configured for IP with Enhanced IGRP as the routing
protocol. This will facilitate your using Telnet to reach the routers and IP ping to troubleshoot basic connectivity.
However, keep in mind that your goal is to get the AppleTalk internetwork running. Don't assume that the AppleTalk
internetwork is working just because IP is working.
Success Criteria
Upon successfully completing this scenario, you should be able to ping each interface of each router with an
AppleTalk ping command.
In addition, you will know that the AppleTalk internetwork is operational and meets policy goals when the Fonda,
Monroe, and Bogart routers can see the following five networks:
The zone list for the Fonda, Monroe, and Bogart routers should look like this:
You will not be able to easily verify that the Fonda router is not propagating the zzzserial zone on its LAN interface.
However, you will be able to verify that the Bogart and Gable routers are not propagating the zzzserial zone by
checking Gable's routing table and zone list. Gable should see the following networks:
Gable should see the following zones:
Network Zone(s)
Net 10-10 zzzserial
Net 20-20 zzzserial
Net 30-30 MarketingAndSales
Net 40-40 Admin
Net 50-50

VirtualTeams
Additional zone for net 50-50: Manufacturing
Name Network(s)
Admin 40-40
MarketingAndSales 30-30
zzzserial 20-20 10-10
VirtualTeams 50-50
Manufacturing 50-50
Network Zone(s)
Net 30-30 MarketingAndSales
Net 40-40 Admin
Net 50-50
VirtualTeams
Additional zone for net 50-50: Manufacturing
CertificationZone Page 9 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
To ensure that Gable is running correctly as a stub router on its Token Ring interface, issue a show appletalk
interface To0 command and verify that the output shows the message, "AppleTalk RTMP stub mode is enabled."
Also, issue a debug appletalk rtmp command and make sure that RTMP packets are being sent out the Token Ring
interface, but they include only an RTMP header, which is necessary for end nodes. The RTMP packets should have
a size of 10 bytes and not include any routes.
To make sure that RTMP packets are not being sent out any serial interfaces, issue a debug appletalk rtmp
command on the Monroe, Fonda, and Bogart routers. The Monroe router should not send any RTMP packets, since it
has only serial ports. The source interface for RTMP packets on Fonda and Bogart should be E0.
You should also ensure that each router is learning routes via the correct routing protocol, Enhanced IGRP or RTMP.
To help you understand this success criterion, you can look at the results of a show appletalk route, show
appletalk zone, and show appletalk eigrp topology for correctly-configured routers by clicking on the following
links:
• Monroe
• Bogart

• Gable
• Fonda
Procedure
As mentioned in the Introduction, the best method to use if you want to emulate the second day of the CCIE test is to
download the provided configuration updates and then use show and debug commands to troubleshoot the problems.
Don't examine the configuration updates first. Just download them. If you prefer, you can develop your own
configurations based on the network drawing in Figure 1. Or, you can study the provided configuration updates before
downloading them and attempt to fix the configurations before using them.
This scenario assumes you have successfully completed AppleTalk Scenario One and have saved the debugged
routers' configurations from Scenario One. If this is not the case, you can erase start, reload, and then download the
basic, non-buggy configurations referenced in the "Tips and Debriefing" section of Scenario One.
Once you have the basic configurations loaded, follow these steps to download the provided configuration updates.
Remember, these updates have bugs. Your job is to troubleshoot them.
1. On each router, go into enable mode and then configuration mode.
2. Open the configuration update file for a router and select all text and copy the text to the clipboard.
3. In your terminal window, paste the commands you copied in the previous step into the appropriate router's
configuration.
4. Repeat steps 2 and 3 for each remaining router.
5. Troubleshoot the problems, and remove and add commands until you have met the success criteria.
Configuration Updates
Name Network(s)
Admin 40-40
MarketingAndSales 30-30
VirtualTeams 50-50
Manufacturing 50-50
Note:
These links should open in new
browser windows. You can open
several at a time and switch
between them. Simply close the

window(s) to return to this
document.
CertificationZone Page 10 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
Each router's configuration updates can be accessed by clicking on the following links:
• Monroe
• Bogart
• Gable
• Fonda
Passwords
The configuration files do not have any passwords assigned to the console or VTY lines. There is an enable password
assigned. The enable password is cisco. There is no enable secret password.
Tips and Debriefing
Do not read this section until you have worked on the lab and have either met the success criteria or have decided
you need some hints.
When troubleshooting, a few tips to keep in mind are as follows:
• If you are Telnetted to the routers, rather than using the console port, then you must issue the terminal monitor
command to see debug output. Don't assume you have met the success criteria until you have ensured that you can
see debug output.
• When making AppleTalk configuration changes, shut down the relevant interfaces first. Make the changes and then
leave the interfaces shut for a minute or two. This gives the routers time to flush old entries in the routing and zone
tables.
• Be sure to have a console cable and terminal software handy when troubleshooting. Because you may shut down
interfaces while troubleshooting, you might not be able to reach all the routers via Telnet.
As you should know by now, each router configuration update has minor bugs and anomalies. To see a list of the
bugs, read Scenario Two Configuration Bugs Revealed.
If you give up, or if you want to verify your completed work, you can view the correct configurations for each router
here:
• Monroe
• Bogart

• Gable
• Fonda
Configuration Bugs Revealed
Do not read this section until you have attempted to solve the problems! This explains the bugs that were inserted
into each router's configuration.
Bogart
• The most serious problem with the provided configurations is that Bogart is using Monroe's Enhanced IGRP for
Note:
These links should open in new
browser windows. You can open
several at a time and switch
between them. Simply close the
window(s) to return to this
document.
Note:
These links should open in new
browser windows. You can open
several at a time and switch
between them. Simply close the
window(s) to return to this
document.
CertificationZone Page 11 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
AppleTalk router ID. Bogart is misconfigured with the router ID 1. Bogart should use router ID 3, per Figure 1. This
causes routes not to appear in other router's routing tables. It also causes port S0 on Bogart and port S1 on Monroe
to be disabled, from AppleTalk's point of view. If you issue a show appletalk interface command, you will see that
these ports display the message, "Remote peer configuration mismatch."
• Once you fix the Enhanced IGRP problem, you should make sure that RTMP packets are not sent out Bogart's S0
port. With the debug appletalk rtmp command you will discover that RTMP packets are in fact being sent. You need
to add the no appletalk send-rtmps command to S0.

• With the debug appletalk rtmp command, you will also notice an anomaly on Bogart's E0 port. Bogart should
advertise only network 50-50. Instead, it advertises 50-50, 10-10, and 20-20. Bogart's configuration is missing the
appletalk zip-reply-filter 600 command, which filters the zzzserial zone. By filtering the zzzserial zone, you also filter
the 10-10 and 20-20 routes from the RTMP packets. This is desired.
• Note that Bogart has appletalk getzonelist-filter 600 configured. This is necessary if there are any end nodes on
the Ethernet LAN. The getzonelist filter filters zones when Macintosh users request a list of zones to fill the Chooser
Window. The zip-reply filter, on the other hand, filters zones when other routers, (in this case router Gable), request
the zone names for a cable range.
Monroe
• With the provided configurations, Monroe incorrectly sends RTMP packets out its S0 and S1 ports. Even configuring
the no appletalk route-redistribution command does not fix the problem. You need to configure the no appletalk
send-rtmps command on both S0 and S1.
Gable
• Once you add the appletalk zip-reply-filter 600 command to Bogart's configuration, Gable should see the correct
network numbers and zones. (You may have to disable and then enable Gable's E0 to cause it to learn the correct
numbers and zones.)
• Using the debug appletalk rtmp command on Gable, you will notice that it does not send any RTMP packets out its
Token Ring interface. This will be a problem if there are end nodes on the Token Ring network, which presumably
there are. Gable is incorrectly configured with the no appletalk send-rtmps command instead of the appletalk rtmp-
stub command.
Fonda
• Until you configure the no appletalk send-rtmps command on Fonda, Fonda incorrectly sends RTMP packets out
its S0 interface
• Fonda should also have an appletalk zip-reply-filter 600 command on its E0 port if there are other routers
reachable via its Ethernet port. Once you add this command, the debug appletalk rtmp command should show that
Fonda advertises only two routes, routes 30-30 and 40-40. Although the basic network drawing does not show any
other routers on Fonda's Ethernet network, it is possible that some will be added in the future, or there are already
other routers that are not on the drawing. The scenario specifically mentions no other routers on the Token Ring LAN,
but does not state this for the Ethernet LANs.
[IE-ApTk-LS2-F02.txt]

[19990802]
[19990804]
CertificationZone Page 12 of 12
/?Issue=2&IssueDate=10-01-1999&CP= 11/06/01
Copyright © 1999 Genium Publishing Corporation