
162 Efficient Networking
P0609327 02
Some network management systems have network planning modules that determine network
flows. These modules provide more detailed and accurate analysis because they can include
correct node, link and routing information. They also help to determine network strength by
conducting link and node failure analysis. By simulating failures, re-loading network and
re-computed routes, the modules indicate where the network can be out of capacity during failures.
Not enough link capacity
If there is not enough link capacity, consider one or more of the following options:
• Use the G.723.1 codec. Compared to the default G.729 codec with 20 ms payload, the G.723.1
codecs use 29% to 33% less bandwidth.
• Upgrade the bandwidth for the links.
Other intranet resource considerations
Bottlenecks caused by non-WAN resources do not occur often. For a more complete evaluation,
consider the impact of incremental IP telephony traffic on routers and LAN resources in the
intranet where the IP telephony traffic moves across LAN segments that are saturated, or routers
whose central processing unit (CPU) utilization is high.
Implementing the network, LAN engineering
To minimize the number of router hops between the systems, connect the gateways to the intranet.
Ensure that there is enough bandwidth on the WAN links shorter routes. Place the gateway and the
LAN router near the WAN backbone. This prevents division of the constant bit-rate IP telephony
traffic from bursty LAN traffic, and makes easier the end-to-end Quality of Service engineering
for packet delay, jitter and packet loss.
Further network analysis
This section describes how to examine the sources of delay and error in the intranet. It also
discusses several methods for reducing one-way delay and packet loss.
The key methods are described under the following headings:
• “Components of delay” on page 163
• “Reduce link delay” on page 163
• “Reducing hop count” on page 164
• “Routing issues” on page 165
Kommentare zu diesen Handbüchern