|
|
This document describes new and changed information for the Cisco 827 Routers Hardware Installation Guide and the Cisco 827 Routers Software Configuration Guide.
For last-minute updates to this release note, refer to the Cisco 827 routers documentation Web site at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/index.htm.
The ADSL cable that you connect to the Cisco 827 router must be 10BaseT Category 5, Unshielded twisted-pair (UTP) cable. Using regular telephone cable can introduce line errors.
Perform the following steps to configure the router for DHCP client support:
Specifying the value client-id ethernet0 means that the MAC address of the Ethernet interface will be used as the client ID when the DHCP request is sent. Otherwise, the MAC address of the BVI interface will be used as the client ID.
Step 2 Configure NAT.
a. Configure the BVI interface by entering the ip nat outside command.
b. Configure the Ethernet interface by entering the ip nat inside command.
c. Create an access list under NAT by entering the access-list 1 permit ip address command to match all Ethernet IP addresses.
d. Configure the source list under NAT by entering the
ip nat inside source list 1 interface BVI 1 overload command.
Step 3 Configure the Cisco 827 router to act as a DHCP server. This step is optional.
a. At the config-if router prompt, enter the ip dhcp pool server name command.
b. Enter the import all command to have the Cisco 827 router retrieve the Microsoft Windows nameserver (WINS) and domain name system (DNS) server addresses for name resolution.
The following example shows a configuration of the DHCP client.
Current configuration: ! version 12.0 no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname c827 ! ! ip subnet-zero ip dhcp excluded-address 10.10.10.1 ! ip dhcp pool SERVER network 10.10.10.0 255.255.255.0 default-router 10.10.10.1 import all ! ! ! bridge irb interface Ethernet0 ip address 10.10.10.1 255.255.255.0 no ip directed-broadcast ip nat inside ! interface ATM0 no ip address no ip directed-broadcast no atm ilmi-keepalive bundle-enable hold-queue 208 in ! interface ATM0.1 point-to-point no ip directed-broadcast pvc 1/100 encapsulation aal5snap ! bridge-group 1 ! interface ATM0.2 point-to-point ip address 5.0.0.2 255.0.0.0 no ip directed-broadcast pvc 1/101 protocol ip 5.0.0.1 broadcast protocol ip 5.0.0.5 broadcast encapsulation aal5snap ! ! interface BVI1 ip address dhcp client-id Ethernet0 no ip directed-broadcast ip nat outside ! ip nat inside source list 1 interface BVI1 overload ip classless ip route 0.0.0.0 0.0.0.0 BVI1 no ip http server ! access-list 1 permit 10.10.10.0 0.0.0.255 bridge 1 protocol ieee bridge 1 route ip ! voice-port 1 timing hookflash-in 0 ! voice-port 2 timing hookflash-in 0 ! voice-port 3 timing hookflash-in 0 ! voice-port 4 timing hookflash-in 0 ! ! line con 0 exec-timeout 0 0 transport input none stopbits 1 line vty 0 4 password lab login ! scheduler max-task-time 5000 end
The "Configuring the Dialer Interface" section in "Feature-By-Feature Router Configurations," of the Cisco 827 Routers Software Configuration Guide has an incorrect router prompt in Step 4. The prompt should be Router(config-if).
The "Configuring Easy IP (Phase 1)" section in "Feature-By-Feature Router Configurations," of the Cisco 827 Routers Software Configuration Guide has an incorrect reference in Step 2. The task should refer to the access list defined in Step 1 rather than in Step 2.
Multilink PPP fragments large data packets so that small voice packets can be interleaved within them. However, apart from first-in-first-out (FIFO) queuing, no other kind of output queuing mechanisms are currently supported with PPP over ATM. Consequently, when multilink PPP is configured on the Cisco 827 routers, the big packets are fragmented, but interleaving of small voice packets within them does not occur.
Currently, NAT does not support alerting H.225 messages. Because of that, NAT communication cannot be established between the router end points.
NAT support for H.323 signaling is limited to the Netmeeting application.
PPP over AAL5SNAP encapsulation is currently not supported, although the context-sensitive help mentions that it can be configured.
This feature supports the PPP over Ethernet (PPPoE) client on an ATM permanent virtual circuit (PVC). Only one PPPoE client on a single ATM PVC is supported. The PPPoE client over an ATM interface is supported for all 820 platforms.
The following figure depicts a typical deployment scenario for PPPoE support:
A PPPoE session is initiated on the client side by the network described above. If the session has a timeout or is disconnected, the PPPoE client immediately attempts to reestablish the session.
Follow these steps to configure the router for PPPoE client support:
a. Enter the vpdn enable command in global configuration mode.
b. Configure the vpdn group by entering the vpdn group tag command.
c. Specify the dialing direction by entering the request-dialin command in the vpdn group.
d. Specify the type of protocol in the vpdn group by entering the protocol pppoe command.
Step 2 Configure the ATM interface with PPPoE support.
a. Configure the ATM interface by entering the interface atm 0 command.
b. Specify the ATM PVC by entering the pvc number command.
c. Configure the PPPoE client and specify the dialer interface to use for cloning by entering the pppoe-client dial-pool-number number command.
Step 3 Configure the dialer interface by entering the int dialer number command.
a. Configure the ip address as negotiated by entering the ip address negotiated command.
b. Configure authentication for your network by entering the ppp authentication protocol command. This step is optional.
c. Configure the dialer pool number by entering the dialer pool number command.
d. Configure the dialer-group number by entering the dialer-group number command.
Also configure a dialer list corresponding to the dialer-group:
e. Configure a dialer list corresponding to the dialer-group by entering the dialer-list 1 protocol ip permit command.
 |
Note There can be multiple PPPoE clients each running on a different PVCs, in which case, each client has to use a separate dialer interface and a separate dialer pool, and the PPP parameters need to be applied on the dialer interface. |
If you enter the clear vpdn tunnel pppoe command with a PPPoE client session already established, the PPPoE client session terminates and the PPPoE client immediately tries to reestablish the session.
The following example shows a configuration of a PPPoE client.
vpdn enable vpdn-group 1 request-dialin protocol pppoe int atm0 pvc 1/100 pppoe-client dial-pool-number 1 int dialer 1 ip address negotiated ppp authentication chap dialer pool 1 dialer-group 1
The following MIBs are supported in the Cisco 827 routers:
ADSL-LINE-MIB
ADSL-DMT-LINE-MIB
ATM-FORUM-MIB (not supported per Jenness)
ATM-FORUM-ADDR-REG (not supported per Jenness)
ATM-MIB
CISCO-AAL5-MIB
CISCO-ADSL-DMT-LINE-MIB
CISCO-ATM-EXT-MIB
CISCO-BULK-FILE-MIB
CISCO-CAR-MIB
CISCO-DIAL-CONTROL-MIB
CISCO-FLASH-MIB
CISCO-IETF-ATM2-PVCTRAP-MIB
CISCO-IMAGE-MIB
CISCO-IP-STAT-MIB
CISCO-MEMORY-POOL-MIB
CISCO-PING-MIB
CISCO-QUEUE-MIB
CISCO-RAS-MIB
CISCO-SNAPSHOT-MIB
CISCO-STACKMAKER-MIB
CISCO-SYSLOG-MIB
CISCO-TCP-MIB
CISCO-VOICE-ANALOG-IF-MIB
CISCO-VOICE-COMMON-DIAL-CONTROL-MIB
CISCO-VOICE-DIAL-CONTROL-MIB
CISCO-VOICE-IF-MIB
DIAL-CONTROL-MIB
ENTITY-MIB
IF-MIB
IGMP-MIB
INT-SERV-GUARANTEED-MIB
INT-SERV-MIB
IPMROUTE-MIB
NOVELL-IPX-MIB
NOVELL-RIPSAP-MIB
OLD-CISCO-CHASSIS-MIB
OLD-CISCO-CPU-MIB
OLD-CISCO-INTERFACE-MIB
OLD-CISCO-IP-MIB
OLD-CISCO-MEMORY-MIB
OLD-CISCO-NOVELL-MIB
OLD-CISCO-SYSTEM-MIB
OLD-CISCO-TCP-MIB
PIM-MIB
RFC1398-MIB (ETHERMIB)
RFC1213-MIB
RSVP-MIB
SNMPv2-MIB
TCP-MIB
UDP-MIB
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Posted: Fri Aug 25 10:31:26 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.