Filter
Top Products
Telco and ISP Dial Scenarios and Configurations
Large-Scale POPs
DNC-320
Cisco IOS Dial Services Configuration Guide: Network Services
Note An offload server will always serve as the bundlemaster by bidding a higher value than the
other devices.
Using L2F
L2F is a critical component used in multichassis multilink sessions. If an access server is not in charge
of a multilink session, the access server encapsulates the fragmented PPP frames and forwards them to
the bundlemaster using L2F. The master device receives the calls, not through the dial port (such as a
dual T1/PRI card), but through the LAN or Ethernet port. L2F simply tunnels packet fragments to the
device that owns the multilink session for the call. If you include an offload server in your dial-in
scenario, it creates all the virtual interfaces, owns all the multilink sessions, and reassembles all the
fragmented packets received by L2F via the other stackgroup members. (Refer to Figure 56.)
Stack Group of Access Servers Using MMP with an Offload Processor
Examples
The following sections provide examples for the devices shown in Figure 56:
• Cisco AS5200 Access Server #1
• Cisco AS5200 Access Server #2
• Cisco AS5200 Access Server #3
• Cisco 7206 as Offload Server
• RADIUS Remote Security Examples
Note Be sure to include your own IP addresses, host names, and security passwords
where appropriate.
Cisco AS5200 Access Server #1
The following example runs on the Cisco AS5200 access server labeled #1 in Figure 56:
!
version 11.2
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
no service udp-small-servers
no service tcp-small-servers
!
hostname AS5200-1
!
aaa new-model
aaa authentication login default local
aaa authentication login console enable
aaa authentication login vty local
aaa authentication login dialin radius
aaa authentication ppp default local
aaa authentication ppp dialin if-needed radius
aaa authorization exec local radius
aaa authorization network radius