Page 171 / 196 Scroll up to view Page 166 - 170
B-7
Cisco 850 Series and Cisco 870 Series Access Routers Software Configuration Guide
OL-5332-01
Appendix B
Concepts
NAT
line is up, the backup interface is placed in standby mode. In standby mode, the backup interface is
effectively shut down until it is enabled. Any route associated with the backup interface does not appear
in the routing table.
Because the backup interface command is dependent on the router’s identifying that an interface is
physically down, it is commonly used to back up ISDN BRI connections, asynchronous lines, and leased
lines. The interfaces to such connections go down when the primary line fails, and the backup interface
quickly identifies such failures.
Floating Static Routes
Floating static routes are static routes that have an administrative distance greater than the administrative
distance of dynamic routes. Administrative distances can be configured on a static route so that the static
route is less desirable than a dynamic route. In this manner, the static route is not used when the dynamic
route is available. However, if the dynamic route is lost, the static route can take over, and the traffic can
be sent through this alternative route. If this alternative route uses a dial-on-demand routing (DDR)
interface, then that interface can be used as a backup feature.
Dialer Watch
Dialer watch is a backup feature that integrates dial backup with routing capabilities. Dialer watch
provides reliable connectivity without having to define traffic of interest to trigger outgoing calls at the
central router. Hence, dialer watch can be considered regular DDR with no requirement for traffic of
interest. By configuring a set of watched routes that define the primary interface, you are able to monitor
and track the status of the primary interface as watched routes are added and deleted.
When a watched route is deleted, dialer watch checks for at least one valid route for any of the IP
addresses or networks being watched. If there is no valid route, the primary line is considered down and
unusable. If there is a valid route for at least one of the watched IP networks defined and the route is
pointing to an interface other than the backup interface configured for dialer watch, the primary link is
considered up and dialer watch does not initiate the backup link.
NAT
Network Address Translation (NAT) provides a mechanism for a privately addressed network to access
registered networks, such as the Internet, without requiring a registered subnet address. This mechanism
eliminates the need for host renumbering and allows the same IP address range to be used in multiple
intranets.
NAT is configured on the router at the border of an
inside network
(a network that uses nonregistered IP
addresses) and an
outside network
(a network that uses a globally unique IP address; in this case, the
Internet). NAT translates the inside local addresses (the nonregistered IP addresses assigned to hosts on
the inside network) into globally unique IP addresses before sending packets to the outside network.
With NAT, the inside network continues to use its existing private or obsolete addresses. These addresses
are converted into legal addresses before packets are forwarded onto the outside network. The translation
function is compatible with standard routing; the feature is required only on the router connecting the
inside network to the outside domain.
Page 172 / 196
B-8
Cisco 850 Series and Cisco 870 Series Access Routers Software Configuration Guide
OL-5332-01
Appendix B
Concepts
Easy IP (Phase 1)
Translations can be static or dynamic. A static address translation establishes a one-to-one mapping
between the inside network and the outside domain. Dynamic address translations are defined by
describing the local addresses to be translated and the pool of addresses from which to allocate outside
addresses. Allocation occurs in numeric order, and multiple pools of contiguous address blocks can be
defined.
NAT eliminates the need to readdress all hosts that require external access, saving time and money. It
also conserves addresses through application port-level multiplexing. With NAT, internal hosts can share
a single registered IP address for all external communications. In this type of configuration, relatively
few external addresses are required to support many internal hosts, thus conserving IP addresses.
Because the addressing scheme on the inside network may conflict with registered addresses already
assigned within the Internet, NAT can support a separate address pool for overlapping networks and
translate as appropriate.
Easy IP (Phase 1)
The Easy IP (Phase 1) feature combines Network Address Translation (NAT) and PPP/Internet Protocol
Control Protocol (IPCP). This feature enables a Cisco router to automatically negotiate its own
registered WAN interface IP address from a central server and to enable all remote hosts to access the
Internet using this single registered IP address. Because Easy IP (Phase 1) uses existing port-level
multiplexed NAT functionality within Cisco IOS software, IP addresses on the remote LAN are invisible
to the Internet.
The Easy IP (Phase 1) feature combines NAT and PPP/IPCP. With NAT, the router translates the
nonregistered IP addresses used by the LAN devices into the globally unique IP address used by the
dialer interface. The ability of multiple LAN devices to use the same globally unique IP address is known
as
overloading
. NAT is configured on the router at the border of an inside network (a network that uses
nonregistered IP addresses) and an outside network (a network that uses a globally unique IP address; in
this case, the Internet).
With PPP/IPCP, Cisco routers automatically negotiate a globally unique (registered) IP address for the
dialer interface from the ISP router.
Easy IP (Phase 2)
The Easy IP (Phase 2) feature combines Dynamic Host Configuration Protocol (DHCP) server and relay.
DHCP is a client-server protocol that enables devices on an IP network (the DHCP clients) to request
configuration information from a DHCP server. DHCP allocates network addresses from a central pool
on an as-needed basis. DHCP is useful for assigning IP addresses to hosts connected to the network
temporarily or for sharing a limited pool of IP addresses among a group of hosts that do not need
permanent IP addresses.
DHCP frees you from having to assign an IP address to each client manually.
DHCP configures the router to forward UDP broadcasts, including IP address requests, from DHCP
clients. DHCP allows for increased automation and fewer network administration problems by:
Eliminating the need for the manual configuration of individual computers, printers, and shared file
systems
Preventing the simultaneous use of the same IP address by two clients
Allowing configuration from a central site
Page 173 / 196
B-9
Cisco 850 Series and Cisco 870 Series Access Routers Software Configuration Guide
OL-5332-01
Appendix B
Concepts
QoS
QoS
This section describes Quality of Service (QoS) parameters, including the following:
IP Precedence
PPP Fragmentation and Interleaving
CBWFQ
RSVP
Low Latency Queuing
QoS refers to the capability of a network to provide better service to selected network traffic over various
technologies, including ATM, Ethernet and IEEE 802.1 networks, and IP-routed networks that may use
any or all of these underlying technologies. Primary goals of QoS include dedicated bandwidth,
controlled jitter and latency (required by some real-time and interactive traffic), and improved loss
characteristics. QoS technologies provide the elemental building blocks for future business applications
in campus, WAN, and service provider networks.
QoS must be configured throughout your network, not just on your router running VoIP, to improve voice
network performance. Not all QoS techniques are appropriate for all network routers. Edge routers and
backbone routers in your network do not necessarily perform the same operations; the QoS tasks they
perform might differ as well. To configure your IP network for real-time voice traffic, you need to
consider the functions of both edge and backbone routers in your network.
QoS software enables complex networks to control and predictably service a variety of networked
applications and traffic types. Almost any network can take advantage of QoS for optimum efficiency,
whether it is a small corporate network, an Internet service provider, or an enterprise network.
IP Precedence
You can partition traffic in up to six classes of service using IP Precedence (two others are reserved for
internal network use). The queuing technologies throughout the network can then use this signal to
expedite handling.
Features such as policy-based routing and committed access rate (CAR) can be used to set precedence
based on extended access-list classification. This allows considerable flexibility for precedence
assignment, including assignment by application or user, by destination and source subnet, and so on.
Typically this functionality is deployed as close to the edge of the network (or administrative domain)
as possible, so that each subsequent network element can provide service based on the determined policy.
IP Precedence can also be set in the host or network client with the signaling used optionally. IP
Precedence enables service classes to be established using existing network queuing mechanisms (such
as class-based weighted fair queueing [CBWFQ]) with no changes to existing applications or
complicated network requirements.
PPP Fragmentation and Interleaving
With multiclass multilink PPP interleaving, large packets can be multilink-encapsulated and fragmented
into smaller packets to satisfy the delay requirements of real-time voice traffic; small real-time packets,
which are not multilink encapsulated, are transmitted between fragments of the large packets. The
interleaving feature also provides a special transmit queue for the smaller, delay-sensitive packets,
enabling them to be transmitted earlier than other flows. Interleaving provides the delay bounds for
delay-sensitive voice packets on a slow link that is used for other best-effort traffic.
Page 174 / 196
B-10
Cisco 850 Series and Cisco 870 Series Access Routers Software Configuration Guide
OL-5332-01
Appendix B
Concepts
QoS
In general, multilink PPP with interleaving is used in conjunction with CBWFQ and RSVP or IP
Precedence to ensure voice packet delivery. Use multilink PPP with interleaving and CBWFQ to define
how data is managed; use Resource Reservation Protocol (RSVP) or IP Precedence to give priority to
voice packets.
CBWFQ
In general, class-based weighted fair queuing
(
CBWFQ) is used in conjunction with multilink PPP and
interleaving and RSVP or IP Precedence to ensure voice packet delivery. CBWFQ is used with multilink
PPP to define how data is managed; RSVP or IP Precedence is used to give priority to voice packets.
There are two levels of queueing; ATM queues and Cisco IOS queues. CBWFQ is applied to Cisco IOS
queues. A first-in-first-out (FIFO) Cisco IOS queue is automatically created when a PVC is created. If
you use CBWFQ to create classes and attach them to a PVC, a queue is created for each class.
CBWFQ ensures that queues have sufficient bandwidth and that traffic gets predictable service.
Low-volume traffic streams are preferred; high-volume traffic streams share the remaining capacity,
obtaining equal or proportional bandwidth.
RSVP
RSVP enables routers to reserve enough bandwidth on an interface to ensure reliability and quality
performance. RSVP allows end systems to request a particular QoS from the network. Real-time voice
traffic requires network consistency. Without consistent QoS, real-time traffic can experience jitter,
insufficient bandwidth, delay variations, or information loss. RSVP works in conjunction with current
queuing mechanisms. It is up to the interface queuing mechanism (such as CBWFQ) to implement the
reservation.
RSVP works well on PPP, HDLC, and similar serial-line interfaces. It does not work well on
multi-access LANs. RSVP can be equated to a dynamic access list for packet flows.
You should configure RSVP to ensure QoS if the following conditions describe your network:
Small-scale voice network implementation
Links slower than 2 Mbps
Links with high utilization
Need for the best possible voice quality
Low Latency Queuing
Low latency queuing (LLQ) provides a low-latency strict priority transmit queue for real-time traffic.
Strict priority queuing allows delay-sensitive data to be dequeued and sent first (before packets in other
queues are dequeued), giving delay-sensitive data preferential treatment over other traffic.
Page 175 / 196
B-11
Cisco 850 Series and Cisco 870 Series Access Routers Software Configuration Guide
OL-5332-01
Appendix B
Concepts
Access Lists
Access Lists
With basic standard and static extended access lists, you can approximate session filtering by using the
established keyword with the
permit
command. The established keyword filters TCP packets based on
whether the ACK or RST bits are set. (Set ACK or RST bits indicate that the packet is not the first in the
session and the packet therefore belongs to an established session.) This filter criterion would be part of
an access list applied permanently to an interface.

Rate

4.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top