implementing. Another important issue might be designing for redundancy with DDR. These
are the most popular design considerations, so they are covered in this section.
needs some consideration. For example, is any tunneling being performed on the router? How
about DLSW activity? These things might affect the throughput across a Frame Relay network.
The CPU utilization and processes need to be checked and tended, especially if CPU-intensive
configurations are being used. The Cisco command show process is the CCDP's friend. It
details the processes and shows how much CPU time the processes consume. If the processor
shows high levels of utilization, it might be time to upgrade the router. See Example 10-6.
the number of access lines, the number of PVCs (which usually drive the cost), and so on.
and a number of remote sites. Remember to provide enough bandwidth to the central site, and
do the bandwidth arithmetic to make sure that oversubscription won't be a problem. A star
topology is depicted in Figure 10-21. Here are some benefits of a star topology:
Frame Relay providers. They assign the same DLCI to the remotes and different DLCI numbers
at the central site. This makes troubleshooting easier because the engineers have to remember
only one DLCI number for the remote sites.
of at least 192 K to accommodate the remote sites if there is a need to avoid oversubscription.
CPU utilization for five seconds: 15%/11%; one minute: 13%; five minutes: 11%
PID QTy PC Runtime (ms) Invoked uSecs Stacks TTY Process
1 Csp 31E4C2E 47360 137744 343 732/1000 0 Load Meter
2 ME 31672CC 24976 727 34354 2040/4000 18 Virtual Exec
3 Lst 31D54F6 2161368 123031 17567 3704/4000 0 Check heaps
4 Cwe 31DB6E6 0 1 0 3728/4000 0 Pool Manager
5 Mst 315FE36 0 2 0 3696/4000 0 Timers
6 Mwe 30F682A 37384 2519 14840 3636/4000