| 5.5.4 |
You
have just installed a new branch office that will use DDR to dial
into your central site.
The next step is to configure routing so the branch office
can successfully communicate with the central site using TCP/IP.
You will need to install a default route at the branch office
pointing back at the central site.
At the central site you will need to add a static route for
the branch office Ethernet network pointing back at the branch
office router.
To ensure that the branch office can communicate with the
rest of the central site, redistribute the static route to the core
network running IGRP. |
| 5.5.5 |
Given a
Central site Cisco-IOS router with ISDN BRI capability and a branch
office site Cisco-IOS router with ISDN BRI capability, configure
both routers so that you can place an ISDN call between your two
company sites. |
| 5.5.6 |
The
Denver office needs to control what interesting traffic will bring
up the ISDN connection to the Phoenix office.
You will setup an extended ACL and apply it to the dialer
group. |
| 5.5.10 |
The Phoenix
and Denver offices want to exchange routing updates without
incurring large telecommunication bills. Your solution is to
configure snapshot routing between the two routers. |
| 5.6.1 |
Configure
the branch office router and central site router to dial two B
channels for a total link speed of 128kbps.
Use two dialer maps to dial the two phone numbers and enable
PPP multilink. |
| 5.6.5 |
You have other
ISDN devices connected to the same ISDN line that your central
router is connected to (this is possible with an S/T Interface).
To ensure that they don’t step on each other, we want to
configure the central router to only answer calls that are placed to
the 5554000 number.
|
| 5.8.1 |
Given
a Central site Cisco-IOS router with ISDN PRI capability and branch
office site Cisco-IOS routers with ISDN BRI capability, configure
all routers so that you can place an ISDN call between your three
company sites. |