|
|
This chapter tells you how to perform basic configuration for the Cisco 6400 node route processor (NRP). The Cisco 6400 can contain multiple NRP modules, configured to operate independently or as redundant pairs (1+1). The chapter contains the following sections:
The following methods are available for configuring the NRP using the command-line interface (CLI):
You might need the following information before you configure the NRP:
Complete the following steps to configure the NRP manually:
Step 1 Use a network management application, connect a console terminal or a terminal server to the NRP console port on the front bulkhead.
Step 2 After you boot the NRP, the following information is displayed to verify that the router has booted successfully. Note the Cisco IOS software version (identified with the arrow below).
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) C6400R Software (C6400R-P5-M), Version 12.0(5)DB
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Fri 30-Apr-99 01:51 by jdoe
Image text-base: 0x600088F8, data-base: 0x608EE000
cisco NRP (NRP1) processor with 114688K/16384K bytes of memory.
R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 1024KB L2 Cache
Last reset from BOOTFLASH:
X.25 software, Version 3.0.0.
Bridging software.
2 Ethernet/IEEE 802.3 interface(s)
1 FastEthernet/IEEE 802.3 interface(s)
1 ATM network interface(s)
125K bytes of non-volatile configuration memory.
4096K bytes of Boot flash ROM (Sector size 256K).
8192K bytes of Flash SIMM (Sector size 256K).
Secondary not up
Press RETURN to get started!
Step 3 If your NRP contains an older software image, you will see the following prompt:
--- System Configuration Dialog --- At any point you may enter a question mark '?' for help. Use Ctrl-Z cutler-c to abort configuration dialog at any prompt. Default settings are in square brackets '[]'. Would you like to enter the initial configuration dialog? [yes/no]:
Enter yes to use the setup facility. Proceed to the "Using the Setup Facility" section.
Step 4 Press Return. After a few seconds, the user EXEC prompt (Router>) is displayed. Type enable to enter enable mode (configuration changes can be made only when you are in enable mode):
Router> enable Router#
The prompt changes to the privileged EXEC prompt.
Step 5 Enter the config terminal command at the privileged EXEC prompt to enter configuration mode from the terminal:
Router# config terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
The prompt changes to the configuration mode prompt.
Step 6 Enter the enable secret password (which is a very secure, encrypted password) and the enable password (which is less secure, or nonencrypted, password). The passwords should be different for maximum security. The following example sets the enable secret password to walnut and the enable password to pecan:
Router(config)# enable secret walnut Router(config)# enable pecan
An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric characters; an enable password or virtual terminal password can contain any number of uppercase and lowercase alphanumeric characters. In all cases, a number cannot be the first character. Spaces are also valid password characters. Leading spaces are ignored; trailing spaces are recognized.
Step 7 Enter a host name for the NRP. The host name will appear in the CLI prompt; the default host name is Router.
Router(config)# hostname NRP1 NRP1(config)#
Step 8 If you are upgrading the NRP from an older software version, you must configure the NRP to use the combined network management Ethernet (NME) interface on the NSP. Perform the following task to enable the combined NME interface:
Router(config)# interface ethernet 0/0/0 Router(config-if)# no ip address Router(config-if)# interface ethernet 0/0/1
Router(config-if)# ip address negotiated Router(config-if)# ^Z
If your NRP does not use a DHCP server to obtain an IP address, you must configure a static IP address instead. Replace the ip address negotiated command above with a static IP address assignment:
Router(config-if)# ip address 172.26.94.158
Step 9 Store the configuration or changes to your startup configuration in NVRAM:
Router# copy system:running-config nvram:startup-config
Using this command saves the configuration settings that you created in the NRP by means of configuration mode and the setup facility. If you fail to enter the command, your configuration will be lost the next time you reload the NRP.
Your NRP is now minimally configured and will boot with the configuration you have entered. To see a list of the configuration commands available to you, enter ? at the prompt or press the help key while you are in configuration mode.
You can check your settings and review any changes to your configuration using various software commands.
To check the value of the runtime settings you have entered, enter the more system:running-config command at the Router# prompt. To review changes you have made to the startup configuration, use the EXEC more nvram:startup-config command to display the information stored in NVRAM.
To confirm the hardware configuration of the NRP on the Cisco 6400, use the show nrp command:
Router# show nrp
Router installed in slot 2
Network IO Interrupt Throttling:
throttle count=0, timer count=0
active=0, configured=0
netint usec=3999, netint mask usec=200
NRP CPU EEPROM:
Hardware revision 2.12 Board revision B0
Serial number 6361674 Part number 255-65535-255
Test history 0x0 RMA number 255-255-255
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 15 02 01 00 61 12 4A 49 06 00 03 00 00 00 00
0x30: 58 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
Router#
File systems on the NRP include read-only memory (NVRAM, or system), Flash memory (such as bootflash and the Flash disk), and remote file systems (such as TFTP or rcp servers). Use the show file systems privileged EXEC command to display the valid file systems on your NSP. For example:
Router# show file systems
File Systems:
Size(b) Free(b) Type Flags Prefixes
- - flash rw sec-flash:
- - flash rw sec-bootflash:
- - nvram rw sec-nvram:
* 3407872 249884 flash rw bootflash:
7602176 3905620 flash rw flash:
- - opaque rw null:
- - opaque rw system:
- - network rw tftp:
129016 128049 nvram rw nvram:
- - opaque wo lex:
- - network rw rcp:
- - network rw ftp:
Router#
Use the dir command to show the contents of a file system. Remember to include the trailing colon in the name of the file system:
Router# dir bootflash: Directory of bootflash:/ 1 -rw- 3157860 Jul 15 2000 03:45:14 c6400r-p5-mz.120-5.DC 3407872 bytes total (249884 bytes free) Router#
If your Cisco 6400 system is configured with redundant NRPs, use the dir command with file systems that begin with sec- to show file systems on the secondary (redundant) NRP. For example, dir sec-nvram: will show the contents of the NVRAM on the secondary NRP.
The setup facility allows quick configuration of common global parameters, including the network management interface.
Step 1 When asked if you want to enter the initial configuration dialog, enter yes or press Return.
Would you like to enter the initial configuration dialog? [yes/no]: yes Basic management setup configures only enough connectivity
for management of the system, extended setup will ask you
to configure each interface on the system
Step 2 When asked if you want to enter basic management setup information, enter yes or press Return.
Would you like to enter basic management setup? [yes/no]: yes
Step 3 Enter a host name for the NRP:
Configuring global parameters: Enter host name [Router]: NRP1
Step 4 Enter the enable secret password, enable password, and virtual terminal password:
The enable secret is a password used to protect access to
privileged EXEC and configuration modes. This password, after
entered, becomes encrypted in the configuration.
Enter enable secret: barney The enable password is used when you do not specify an
enable secret password, with some older software versions, and
some boot images. Enter enable password: wilma The virtual terminal password is used to protect
access to the router over a network interface. Enter virtual terminal password: fred
Step 5 SNMP is the most widely supported open standard for network management. It enables you to access and set configuration and run-time parameters of routers and communication servers. SNMP defines a set of functions that can be used to monitor and control network elements.
Enter yes to accept SNMP management; enter no to refuse it:
Configure SNMP Network Management? [yes]: yes Community string [public]: public
Step 6 When asked if you want to see the current interface summary, enter yes or press Return:
Current interface summary Any interface listed with OK? value "NO" does not have a valid configuration Interface IP-Address OK? Method Status Protocol ATM 0/0/0unassigned NO unset up up Ethernet 0/0/0unassigned NO unset up up Ethernet 0/0/1unassigned NO unset up up FastEthernet 0/0/0unassigned NO unset up down
Step 7 Respond to the prompts as follows, using your own addresses and mask at the setup prompts:
Enter interface name used to connect to the management network from the above interface summary: ethernet0/0/0
Configuring interface Ethernet0/0/0:
Configure IP on this interface? [yes]: yes
IP address for this interface: 172.27.48.136
Subnet mask for this interface [255.255.0.0] : 255.255.252.0
Class B network is 172.27.0.0, 22 subnet bits; mask is /22
The following configuration command script was created:
hostname Router
enable secret 5 $1$8IM2$IclxSoWqZKKQ/M5UCFVh2/
enable password wilma
line vty 0 4
password wilma
snmp-server community public
!
no ip routing
!
interface ATM 0/0/0
shutdown
no ip address
!
interface Ethernet 0/0/0
no shutdown
ip address 172.27.48.136 255.255.252.0
!
interface FastEthernet 0/0/0
shutdown
no ip address
!
end
[0] Go to the IOS command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration to nvram and exit.
Step 8 Check the Ethernet interface IP parameters (indicated with the arrow), and save the configuration to NVRAM:
Enter your selection [2]: 2 Building configuration... Use the enabled mode 'configure' command to modify this configuration.
Your NRP is now minimally configured and ready to use. You can use the setup command if you want to modify the parameters after the initial configuration.
Permanent virtual circuits (PVCs) are used to connect the NRP to node line card (NLC) ATM interfaces on the Cisco 6400 chassis. Typically, each subscriber is bound to a specific NRP and should be configured as a separate PVC.
The following sections describe common PVC configuration tasks:
For more information on configuring PVCs, refer to "Configuring ATM" in the Cisco IOS Wide-Area Networking Configuration Guide.
| Step | Command | Description | ||
|---|---|---|---|---|
| interface atm 0/0/0 [.subinterface-number {multipoint | point-to-point} ] | Specify the ATM interface and optional subinterface. | ||
| pvc [name] vpi/vci | Configure a new ATM PVC by assigning a name (optional) and VPI/VCI numbers. | ||
| encapsulation aal-encap [ppp virtual-template1 number] | Configure the ATM adaptation layer (AAL) and encapsulation type, and optionally configure a PVC to use a virtual-template as the default PPP interface configuration. |
| 1A virtual template assigns PPP features (such as authentication and IP address assignment method) to a PVC. Virtual templates are used when configuring PPP over ATM. |
The following example shows a typical PVC configuration using the ATM Adaption Layer 5 (AAL5) subnetwork access protocol (SNAP) encapsulation. AAL5 SNAP is commonly used in IP routing and bridging. For configuration tasks, refer to the "Configuring Routing and Bridging" section.
Router(config)# interface atm 0/0/0 Router(config-if)# pvc 0/40 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# ^Z
The following example shows a typical PVC configuration for PPP over ATM. For configuration tasks, refer to the "Configuring PPP over ATM" section.
Router(config)# interface atm 0/0/0 Router(config-if)# pvc 0/41 Router(config-if-atm-vc)# encapsulation aal5mux ppp virtual-Template 1 Router(config-if-atm-vc)# exit Router(config-if)# exit Router(config)# interface virtual-template 1 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# ppp authentication pap
The NRP allows the configuration of multiple virtual interfaces, or subinterfaces, on a single physical interface. The ATM interface on the NRP (interface atm 0/0/0) can be configured with subinterfaces to allow greater flexibility and connectivity when working with subscriber sessions.
A subinterface must be classified as either point-to-point or multipoint. A point-to-point interface supports only a single PVC; a multipoint interface may have be configured with multiple PVCs.
Router(config)# interface atm 0/0/0.20 point-to-point Router(config-subif)# pvc 0/40 Router(config-if-atm-vc)# exit Router(config-subif)# pvc 0/41 P2P Interface already has VC Router(config-subif)# exit Router(config)# interface atm 0/0/0.21 multipoint Router(config-subif)# pvc 0/50 Router(config-if-atm-vc)# exit Router(config-subif)# pvc 0/51 Router(config-if-atm-vc)# exit
A PVC on a multipoint subinterface cannot send data to another PVC on the same subinterface. This means that a multipoint interface offers greater security than a point-to-point interface, at the expense of flexibility.
When an encapsulation type is specified for the main ATM interface (ATM 0/0/0), all PVCs on subinterfaces inherit this encapsulation type. In the following example, PVCs 0/70 and 0/71 on ATM subinterface 0/0/0.40 inherit the AAL5 multiplex (MUX) encapsulation type from the main interface. PVC 0/72 is specifically configured for AAL5 SNAP, overriding the main interface default.
Router(config)# interface atm 0/0/0 Router(config-if)# encapsulation aal5mux ppp virtual-template 1 Router(config)# interface atm 0/0/0.40 multipoint Router(config-subif)# pvc 0/70 Router(config-if-atm-vc)# exit Router(config-subif)# pvc 0/71 Router(config-if-atm-vc)# exit Router(config-subif)# pvc 0/72 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# ^z
| Step | Command | Description | ||
|---|---|---|---|---|
| Create and name a map class. | |||
| encapsulation aal-encap [ppp virtual-template number] | Configure the ATM adaptation layer (AAL) and encapsulation type, and optionally configure a PVC to use a virtual-template as the default PPP interface configuration. | ||
| exit | Return to configuration mode. | ||
| interface atm 0/0/0 [.subinterface-number {multipoint | point-to-point} ] | Specify the ATM interface and optional subinterface. | ||
| Associate a PPP map class. | |||
| pvc [name] vpi/vci | Configure a PVC on the ATM interface or subinterface. |
VC classes can also be applied to a particular PVC, similar to direct PVC configuration. To configure a PVC using a VC class, perform the following steps in the configuration mode:
| Step | Command | Description | ||
|---|---|---|---|---|
| vc-class atm name | Create and name a map class. | ||
| encapsulation aal-encap [ppp virtual-template number] | Configure the ATM adaptation layer (AAL) and encapsulation type, and optionally configure a PVC to use a virtual-template as the default PPP interface configuration. | ||
| exit | Return to configuration mode. | ||
| interface atm 0/0/0 [.subinterface-number {multipoint | point-to-point} ] | Specify the ATM interface and optional subinterface. | ||
| pvc [name] vpi/vci | Configure a PVC on the ATM interface or subinterface. | ||
| Associate a PPP map class with the PVC. |
The following example shows a typical VC class configuration for the Cisco 6400 NRP:
Router(config)# vc-class atm snap Router(config-vc-class)# encapsulation aal5snap Router(config-vc-class)# ip address unnumbered fastethernet 0/0/0 Router(config-vc-class)# exit Router(config)# vc-class atm ppp-atm Router(config-vc-class)# encapsulation aal5mux ppp virtual-template 1 Router(config-vc-class)# exit Router(config)# interface atm 0/0/0 Router(config-if)# class-int snap Router(config-if)# pvc 0/40 Router(config-atm-vc)# exit Router(config-if)# pvc 0/41 Router(config-atm-vc)# exit Router(config-if)# pvc 0/42 Router(config-atm-vc)# ip address 172.25.14.198 255.255.255.0 Router(config-atm-vc)# exit Router(config)# interface atm 0/0/0.2 multipoint Router(config-subif)# pvc 0/43 Router(config-atm-vc)# exit Router(config-subif)# pvc 0/44 Router(config-atm-vc)# class-vc ppp-atm Router(config-atm-vc)# exit
In the configuration above, ATM interface 0/0/0 is assigned the VC class snap. PVCs 0/40 and 0/41 inherit the properties of VC class snap. PVC 0/42 is configured to override the VC class defaults by assigning a static IP address.
ATM subinterface 0/0/0.2 inherits the properties of the main interface, so PVC 0/43 uses the snap VC class as well. PVC 0/44 overrides the default by assigning a different VC class, ppp-atm.
You can configure your router to automatically discover PVCs that are configured on the NSP. The discovered PVCs and their traffic parameters are configured on the ATM main interface or subinterface that you specify. The NRP router receives the PVC parameter information using Interim Local Management Interface (ILMI).
To configure the NRP for PVC discovery, follow these steps starting in global configuration mode:
| Step | Command | Description | ||
|---|---|---|---|---|
| vc-class atm name | Create and name a map class. | ||
| encapsulation aal-encap [virtual-template number] | Configure the ATM adaptation layer (AAL) and encapsulation type, and optionally configure a PVC to use a virtual template as the default PPP interface configuration. | ||
| exit | Return to configuration mode. | ||
| interface atm 0/0/0 | Specify the ATM interface. | ||
| pvc [name] 0/16 ilmi | Configure an ILMI PVC on the main interface. | ||
| exit | Return to configuration mode. | ||
| atm ilmi-pvc-discovery [subinterface] | Enable PVC discovery on the main interface, and optionally specify that discovered PVCs will be assigned to a subinterface.1 | ||
| class-int vc-class-name | Associate a PPP map class with an interface. |
| 1You can assign additional VC classes to subinterfaces. See the second example for subinterface configuration. |
The following example shows a typical PVC discovery configuration for the Cisco 6400 NRP:
Router(config)# vc-class atm ppp-atm Router(config-vc-class)# encapsulation aal5mux ppp virtual-Template 1 Router(config-vc-class)# exit Router(config)# interface atm 0/0/0 Router(config-if)# pvc 0/16 ilmi Router(config-if-atm-vc)# exit Router(config-if)# atm ilmi-pvc-discovery Router(config-if)# class-int ppp-atm
If you want to separate users on a per-VP basis, you can append the "subinterface" keyword to the ilmi-pvc-discovery command. The following example assigns VC classes to each subinterface:
Router(config)# vc-class atm ppp-General Router(config-vc-class)# encapsulation aal5mux ppp virtual-template 1 Router(config-vc-class)# exit Router(config)# vc-class atm ppp-Admin Router(config-vc-class)# encapsulation aal5mux ppp virtual-template 2 Router(config-vc-class)# exit Router(config)# interface atm 0/0/0 Router(config-if)# pvc 0/16 ilmi Router(config-if-atm-vc)# exit Router(config-if)# atm ilmi-pvc-discovery subinterface Router(config-if)# interface ATM 0/0/0.1 multipoint Router(config-subif)# class-int ppp-atm-General Router(config-subif)# interface ATM 0/0/0.2 multipoint Router(config-subif)# class-int ppp-atm-Admin
This causes all VCs with non-zero VPI values to be placed into the subinterface of the corresponding number, for example, if VC 2/123 is reported by the switch, the VC is placed in subinterface ATM0/0/0.2 and uses VC class ppp-Admin and virtual-template 2 as the basic configuration.
The supported traffic parameters are part of the following service categories: Available Bit Rate (ABR), Unspecified Bit Rate (UBR), UBR+, and Variable Bit Rate Non Real-Time (VBR-NRT). Only one of these categories can be specified per PVC so if a new one is entered, it will replace the existing one.
To configure PVC traffic parameters and a quality of service (QoS) for a PVC, use one of the following commands in VC configuration mode or VC class mode:
| Command | Task |
|---|---|
abr peak minimum | Configure the ABR.1 |
ubr peak | Configure the UBR. |
ubr+ peak minimum | Configure the UBR and a minimum guaranteed rate. |
vbr-nrt peak sustain burst | Configure the non real-time VBR. |
| 1All variables are expressed in kilobits per second (Kbps). |
The following PVC is configured with the UBR QoS, at a peak cell rate of 512Kbps:
Router(config)# interface atm 0/0/0 Router(config-if)# pvc 0/40 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# ubr 512 Router(config-if-atm-vc)# ^z
The following VC class is configured with the UBR+ QoS, at a peak cell rate of 384Kbps and minimum cell rate of 128Kbps. The VC class is then assigned to a subinterface.
Router(config)# vc-class atm ppp1 Router(config-vc-class)# ubr+ 384 128 Router(config-vc-class)# encapsulation aal5mux ppp virtual-template 1 Router(config-vc-class)# exit Router(config)# interface atm 0/0/0.15 multipoint Router(config-if)# class-int ppp1 Router(config-if)# pvc 0/80 Router(config-if-atm-vc)# exit Router(config-if)# pvc 0/81 Router(config-if-atm-vc)# ^z
The following tasks provide the minimum steps needed to configure PPP over ATM on the Cisco 6400 NRP. For more information about PPP over ATM, see "Configuring ATM" in the Wide-Area Networking Configuration Guide of the Cisco IOS 12.0 documentation set.
To configure a virtual template, perform these steps starting in global configuration mode:
| Step | Command | Description | ||
|---|---|---|---|---|
| interface virtual-template number | Associate a virtual template with a virtual template interface. | ||
| ip unnumbered fastethernet 0/0/0 | Enable IP on the interface without assigning a specific IP address. | ||
| peer default ip address {pool [poolname] | dhcp } | Specify a dynamic IP address assignment method, either from an IP address pool or a DHCP server. | ||
| Select the authentication protocol and optional secondary protocol. | |||
| exit | Return to global configuration mode. | ||
| ip local pool poolname low-ip-address [high-ip-address] | (Optional) Configure a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface. | ||
| ip dhcp-server {ip-address | name} | (Optional) Specify which DHCP servers to use on your network. |
 | Caution Do not use a static IP assignment within a virtual template; routing problems can occur. Always use the ip unnumbered command when configuring a virtual template. |
The following example shows a typical virtual template configuration for the Cisco 6400 NRP:
Router(config)# interface virtual-template 1 Router(config-if)# ip unnumbered fastethernet 0/0/0 router(config-if)# peer default ip address pool telecommuters Router(config-if)# ppp authentication chap Router(config-if)# exit Router(config)# ip local pool telecommuters 10.36.1.1 10.36.1.254
In the configuration above, it is assumed that all PPP over ATM VCs (users) cloned from virtual template1 will use CHAP authentication and will be allocated an IP address from the pool named "telecommuters" configured on the router. In addition, the local end of the PPP over ATM connection is running without an IP address (recommended). Instead, the IP address of the FastEthernet interface is used for addressability.
To configure a different class of users on the same router, you can provision a separate virtual template interface. The following example uses a DHCP server rather than a local pool, and prefers PAP authentication over CHAP:
Router(config)# interface Virtual-Template 2 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# peer default ip address dhcp Router(config-if)# ppp authentication pap chap Router(config-if)# exit Router(config)# ip dhcp-server 10.5.20.149
Up to 25 virtual templates can be configured.
A AAA authentication database, such as RADIUS or TACACS+, can be used to configure the user's virtual access interface. To configure AAA authentication for PPP over ATM, see the "Configuring AAA Authentication" section for configuration tasks.
After you have configured a virtual template for PPP over ATM, you must configure the PVCs that carry traffic from the NRP to the ATM interfaces. To configure PPP over ATM on a PVC, use the following commands starting in global configuration mode:
| Step | Command | Description | ||
|---|---|---|---|---|
| interface atm 0/0/0 [.subinterface-number {multipoint | point-to-point} ] | Specify the ATM interface and optional subinterface. | ||
| pvc [name] vpi/vci | Configure a new ATM PVC by assigning a name (optional) and VPI/VCI numbers. | ||
| encapsulation aal5mux ppp virtual-Template number | Configure the ATM adaptation layer (AAL) and encapsulation type, and configure a PVC to use a virtual-template as the default PPP interface configuration. |
You can also configure PVCs using VC classes and PVC discovery, as shown in the "Working with Permanent Virtual Circuits" section.
The following example shows a typical configuration for PPP over ATM, using a RADIUS authentication server:
Router(config)# interface virtual-template 1 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# peer default ip address pool telecommuters Router(config-if)# ppp authentication chap Router(config-if)# exit Router(config)# ip local pool telecommuters 10.36.1.1 10.36.1.254 Router(config)# aaa new-model Router(config)# aaa authentication ppp default radius Router(config)# radius-server host 172.31.5.96 Router(config)# radius-server key foo Router(config)# radius-server attribute nas-port format d Router(config)# interface atm 0/0/0.40 multipoint Router(config-subif)# pvc 0/50 Router(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 1 Router(config-if-atm-vc)# exit Router(config-subif)# pvc 0/51 Router(config-if-atm-vc)# encapsulation aal5mux ppp virtual-template 1 Router(config-if-atm-vc)# exit
The global configuration command show atm pvc ppp shows the PPP over ATM characteristics of all PVCs on the ATM interface:
Router# show atm pvc ppp
VCD /
ATM Int. Name VPI VCI Type VCSt VA VASt IP Addr
0/0/0 1 0 33 PVC UP 1 DOWN 10.123.1.1
0/0/0 foo 0 34 PVC UP 2 DOWN 10.123.1.1
The "VA" column shows the virtual-access interface used for this particular PPP over ATM session. A subsequent show interface virtual-access command gives the PPP specific characteristics of the session:
Router# show interface virtual-access 2 Virtual-Access2 is up, line protocol is up Hardware is Virtual Access interface Internet address is 10.123.1.1/24 MTU 1500 bytes, BW 100000 Kbit, DLY 100000 usec, rely 255/255, load 1/255 Encapsulation PPP, loopback not set, keepalive not set DTR is pulsed for 5 seconds on reset LCP Open
Open: IPCP
Bound to ATM0/0/0 VCD: 2, VPI: 0, VCI: 34
Cloned from virtual-template: 1 Last input 01:04:26, output never, output hang never Last clearing of "show interface" counters 5d02h Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 782 packets input, 30414 bytes, 0 no buffer Received 3 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 395 packets output, 5540 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitions
The lines highlighted in this example show the layer 3 protocols enabled on this interface, the VPI and VCI numbers, and the master virtual template from which this virtual access interface was cloned.
Large-scale deployment of PPP user services requires the use of a central database such as TACACS+ or RADIUS to ease the configuration burden. RADIUS or TACACS+ servers, collectively known as authentication, authorization, and accounting (AAA) servers for PPP over ATM (and other media), contain the per-user configuration database, including password authentication and authorization information. For more information about AAA, see the chapter "Authentication, Authorization, and Accounting (AAA)" in the Cisco IOS Security Configuration Guide.
To configure the router to use AAA for PPP authentication only, enter the following configuration commands:
| Step | Command | Description | ||
|---|---|---|---|---|
| Enable the AAA access control model. | |||
| aaa authentication ppp {default | list-name} method1 [method2...] | Specify one or more AAA authentication methods for use on interfaces running PPP. |
The list-name option refers to the name of this particular method list (or default, if it is the default list), and the method option is a list of methods. For example, to configure virtual template 3 to use TACACS+ before RADIUS, and virtual template 4 to use RADIUS before local authentication, you need to enter the following configuration commands:
Router(config)# aaa new-model Router(config)# aaa authentication ppp list1 tacacs+ radius Router(config)# aaa authentication ppp list2 radius local Router(config)# interface virtual-template 3 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# ppp authentication chap list1 Router(config-if)# exit Router(config)# interface virtual-template 4 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# ppp authentication chap list2 Router(config-if)# ^z
Use the aaa authentication ppp command with the method keyword local to specify that the Cisco router or access server will use the local username database for authentication. The following example shows how to configure authentication using the local username database:
Router(config)# aaa new-model Router(config)# aaa authentication ppp default local
To configure the NRP to use a RADIUS server, use the following commands starting in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| radius-server host {hostname | ip-address} [auth-port port-number] [acct-port port-number] | Specify a RADIUS server host. | ||
| Set the encryption key to match that used on the RADIUS server. | |||
| Select the ATM VC extended format (d) for the NAS port field. |
In the following example, a RADIUS server is enabled and identified, and the NAS port field is set to ATM VC extended format:
Router(config)# aaa new-model Router(config)# aaa authentication ppp default radius Router(config)# radius-server host 172.31.5.96 auth-port 1645 acct-port 1646 Router(config)# radius-server key foo Router(config)# radius-server attribute nas-port format d
The authentication and accounting port need not be specified, because they default to 1645 and 1646, respectively.
To configure the NRP to use a TACACS+ server, use the following commands starting in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| tacacs-server host {hostname | ip-address} [single-connection] [port integer] [timeout integer] [key string] | Specify a TACACS+ server host. | ||
| tacacs-server key key | Set the encryption key to match that used on the TACACS+ daemon. |
In the following example, a TACACS+ server is enabled and identified:
Router(config)# aaa new-model Router(config)# aaa authentication ppp default tacacs+ Router(config)# tacacs-server host 172.31.5.96 Router(config)# tacacs-server key foo
In the following, "home gateway" or "HG" is used synonymously with "LNS" (L2TP Network Server), and "network access server" or "NAS" is used synonymously with "LAC" (L2TP Access Concentrator).
The NAS is the aggregation point of PPP sessions into a L2F or L2TP tunnel, typically (although not always) located at a service provider's POP. Use the following commands to enable VPDN on a NAS using L2F or L2TP, beginning in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| username name password secret | Specify the host name or username, and the password to be used for the PAP/CHAP handshake. | ||
| Enable VPDN and inform the router to look for tunnel definitions from an LNS. | |||
| Define a local group number identifier for which other VPDN variables can be assigned.Valid group numbers range between 1 and 3000. | |||
| request dialin [l2f | l2tp] ip ip-address {domain domain-name | dnis dialed-number} | Enable the router to request a dial in tunnel to an IP address, if the dial in user belongs to a specific domain or the dial in user dialed a specific DNIS. | ||
| Specify a local host name that the tunnel will use to identify itself. |
To configure AAA authentication for VPDN, see the "Configuring AAA Authentication" section for configuration tasks.
The following example shows how to configure the NRP as a NAS, including the use of a RADIUS authentication server:
Router(config)# username dsl-server password 0 shared-password Router(config)# vpdn enable Router(config)# vpdn-group 1 Router(config-vpdn)# request dialin l2tp ip 10.1.2.3 domain dsl.net Router(config-vpdn)# exit Router(config)# interface ATM0/0/0.10 subinterface Router(config-if)# pvc 0/40 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# exit Router(config-if)# exit Router(config)# aaa new-model Router(config)# aaa authentication ppp default radius Router(config)# radius-server host 172.45.92.130 auth-port 1645 acct-port 1646 Router(config)# radius-server attribute nas-port format d Router(config)# radius-server key radius-password
The home gateway is the termination point for an L2F or L2TP tunnel. The home gateway initiates outgoing calls and receives incoming calls from the NAS. To configure the home gateway to initiate and receive calls, use the following commands beginning in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| username name password secret | Specify the host name or user name, and the password to be used for the PAP/CHAP handshake. | ||
| vpdn enable | Enable VPDN and inform the router to look for tunnel definitions from a home gateway. | ||
| vpdn-group group-number | Define a local group number identifier for which other VPDN variables can be assigned.Valid group numbers range between 1 and 3000. | ||
| accept dialin [l2f | l2tp | any] virtual-template virtual-template number remote remote-peer-name | Allow the home gateway to accept an open tunnel request from the specified remote peer, define the Layer 2 protocol to use for the tunnel, and identify the virtual template to use for cloning virtual access interfaces. | ||
| local name name | (Optional) Specify a local host name that the tunnel will use to identify itself. | ||
| exit | Return to global configuration mode. | ||
| interface virtual-template number | Create a virtual template interface, and enter interface configuration mode. | ||
| ip unnumbered fastethernet 0/0/0 | Enable IP without assigning a specific IP address on the LAN. | ||
| peer default ip address {pool [poolname] | dhcp } | Specify a dynamic IP address assignment method, either from an IP address pool or a DHCP server. | ||
| ppp authentication [pap | chap] | Enable PAP or CHAP authentication on the virtual template interface, which will be applied to virtual access interfaces. | ||
| exit | Return to global configuration mode. | ||
| ip local pool poolname low-ip-address [high-ip-address] | (Optional) Configure a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface. | ||
| ip dhcp-server {ip-address | name} | (Optional) Specify which DHCP servers to use on your network. |
To configure AAA authentication for VPDN, see the "Configuring AAA Authentication" section for configuration tasks.
The following example shows how to configure the NRP as a home gateway, including the use of a RADIUS authentication server:
Router(config)# username user1@dsl.net password 0 user1-password Router(config)# username user2@dsl.net password 0 user2-password Router(config)# username corporate-gateway password 0 shared-password Router(config)# vpdn enable Router(config)# vpdn-group 1 Router(config-vpdn)# accept dialin any virtual-template 1 remote dsl-server Router(config-vpdn)# exit Router(config)# interface virtual-template 1 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# peer default ip address pool telecommuters Router(config-if)# ppp authentication chap pap Router(config-if)# exit Router(config)# ip local pool telecommuters 10.36.1.1 10.36.1.255 Router(config)# interface ATM0/0/0.2 subinterface Router(config-if)# pvc 0/40 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# exit Router(config-if)# exit Router(config)# aaa new-model Router(config)# aaa authentication ppp default radius Router(config)# radius-server host 172.45.92.130 auth-port 1645 acct-port 1646 Router(config)# radius-server attribute nas-port format d Router(config)# radius-server key radius-password
The following steps describe useful commands for verifying VPDN activity on the NRP.
Step 1 To verify your VPDN configuration, enter the show vpdn command to make sure the tunnels are active:
Router#show vpdn
Active L2F tunnels = 2 NAS Name Gateway Name NAS CLID Gateway CLID State test-mmp test-gateway 272 272 open 121.102.30.99 134.112.30.119 L2F MIDs = 10 Name NAS Name Interface MID State rw56 test-mmp Vi238 1 open rw55 test-mmp Vi240 3 open rw54 test-mmp Vi242 4 open rw57 test-mmp Vi246 7 open rw57 test-mmp Vi248 8 open rw54 test-mmp Vi245 13 open rw55 test-mmp Vi244 14 open rw16 test-mmp Vi249 97 open rw16 test-mmp Vi251 98 open rw56 test-mmp Vi250 100 open
Step 2 Use the show vpdn session command to display VPDN session information. The show vpdn session all command gives more detailed information, including interface, tunnel, username, packets, status, and window statistics.
Router# show vpdn session
L2TP Session Information (Total tunnels=1 sessions=1)
LocID RemID TunID Intf Username State Last Chg
1 1 421 Vi1 vtemp1@dsl.ne est 00:03:20
% No active L2F tunnels
Router# show vpdn session all
L2TP Session Information (Total tunnels=1 sessions=1)
Call id 1 is up on tunnel id 421
Remote tunnel name is corporate-gateway
Internet Address is 10.1.121.2
Session username is vtemp1@dsl.net, state is established
Time since change 00:03:24, interface Vi1
Remote call id is 1
43 packets sent, 43 received, 1112 bytes sent, 1112 received
Sequencing is off
Remote has not requested congestion control
% No active L2F tunnels
Step 3 Use the show vpdn tunnel command to display VPDN tunnel information. The show vpdn tunnel all command gives more detailed information, including tunnel protocol, id, local and remote tunnel names, packets sent and received, and transport status.
Router# show vpdn tunnel
L2TP Tunnel Information (Total tunnels=1 sessions=1)
LocID RemID Remote Name State Remote Address Port Sessions
421 21 corporate-gat est 10.1.121.2 1701 1
% No active L2F tunnels
Router# show vpdn tunnel all
L2TP Tunnel Information (Total tunnels=1 sessions=1)
Tunnel id 421 is up, remote id is 21, 1 active session
Tunnel state is established, time since change 00:10:37
Peer tunnel name is corporate-gateway
Internet Address 10.1.121.2, port 1701
Local tunnel name is dsl-server
Internet Address 10.1.121.1, port 1701
130 packets sent, 130 received, 3374 bytes sent, 3374 received
Control Ss 4, Sr 2
% No active L2F tunnels
The Point-to-Point Protocol over Ethernet (PPPoE) feature allows a PPP session to be initiated on a simple bridging Ethernet connected client. The session is transported over the ATM link via encapsulated Ethernet-bridged frames. The session can be terminated at either a local exchange carrier central office or an Internet service provider (ISP) point of presence.
In order to gain maximum packet switching performance, Cisco Express Forwarding (CEF) should be enabled on the virtual-access interface. For information about enabling Cisco Express Forwarding, refer to the section "Configuring Cisco Express Forwarding" in the chapter "Cisco Express Forwarding" of the Cisco IOS Switching Services Configuration Guide for IOS Release 12.0.
Perform the following tasks to configure PPP over Ethernet on the Cisco 6400 NRP:
To configure PPP over Ethernet on a virtual-access interface, use the following commands starting in global configuration mode.
| Step | Command | Description | ||
|---|---|---|---|---|
| vpdn enable | Enable virtual private dial-up networking. | ||
| vpdn-group number | Select VPDN-group configuration mode. | ||
| accept dialin pppoe virtual-template number | Configure the router to accept dial-in PPPoE calls. | ||
| pppoe limit per-mac number | (optional) Limit the number of PPPoE sessions that originate from one MAC address. Default is 100. | ||
| pppoe limit per-vc number | (optional) Limit the number of PPPoE sessions that can be established on a virtual circuit. Default is 100. | ||
| exit | Return to global configuration mode. | ||
| virtual-template template-number pre-clone number | (optional) Create "pre-cloned" virtual-access interfaces equal to the expected maximum number of concurrent PPPoE sessions.1 | ||
| ip cef | Enable Cisco Express Forwarding (CEF) on the virtual template. CEF is required for PPPoE. | ||
| interface virtual-template number | Select the virtual-access interface to be configured. | ||
| ip unnumbered fastethernet 0/0/0 | Enable IP on the interface without specifying an address. If you wish to specify an IP address, use the ip address command instead. | ||
| Set the IP MTU to 1492. This is required for PPPoE. | |||
| peer default ip address [pool [poolname] | dhcp] | Specify a dynamic IP address assignment method, either from an IP address pool or a DHCP server. | ||
| ppp authentication [pap | chap] | Select the authentication protocol. |
| Caution Do not use a static IP assignment within a virtual template; routing problems can occur. Always use the ip unnumbered command when configuring a virtual template. |
To configure AAA authentication for PPP over Ethernet, see the "Configuring AAA Authentication" section for configuration tasks.
In the following example, a virtual template is created with 500 pre-cloned virtual-access interfaces:
Router(config)# vpdn enable Router(config)# vpdn-group 1 Router(config-vpdn)# accept dialin pppoe virtual-template 1 Router(config-vpdn)# exit Router(config)# virtual-template 1 pre-clone 500 Router(config)# ip cef Router(config)# interface virtual-template 1 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# ip mtu 1492 Router(config-if)# exit
After you have configured a virtual template for PPP over Ethernet, you must configure the PVCs that carry traffic from the NRP to the ATM interfaces. To configure PPP over Ethernet on an ATM PVC, use the following commands starting in global configuration mode:
| Step | Command | Description | ||
|---|---|---|---|---|
| interface atm 0/0/0.subinterface multipoint | Specify an ATM multipoint subinterface. | ||
| pvc | Configure the PVC. | ||
| encapsulation aal5snap | Configure SNAP encapsulation. | ||
| protocol pppoe | Select PPPoE as the protocol for the PVC. | ||
| exit | Return to global configuration mode. |
You can also configure PVCs using VC classes and PVC discovery, as shown in "Working with Permanent Virtual Circuits" section.
In the following example, PPPoE is enabled directly on an ATM interface:
Router(config)# vpdn enable Router(config)# vpdn-group 1 Router(config-vpdn)# accept dialin pppoe virtual-template 1 Router(config-vpdn)# exit Router(config)# virtual-template 1 pre-clone 500 Router(config)# ip cef Router(config)# interface virtual-template 1 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# ip mtu 1492 Router(config-if)# exit Router(config)# interface atm 0/0/0.1 multipoint Router(config-subif)# pvc 0/60 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# protocol pppoe Router(config-if-atm-vc)# exit Router(config-subif)# pvc 0/61 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# protocol pppoe Router(config-if-atm-vc)# ^z
In the following example, PPPoE is configured on a VC class called users. This VC class is then applied to a particular PVC:
Router(config)# vpdn enable Router(config)# vpdn-group 1 Router(config-vpdn)# accept dialin pppoe virtual-template 1 Router(config-vpdn)# exit Router(config)# virtual-template 1 pre-clone 500 Router(config)# ip cef Router(config)# interface virtual-template 1 Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# ip mtu 1492 Router(config-if)# exit Router(config)# interface atm 0/0/0.1 point-to-point Router(config-if)# pvc 0/60 Router(config-if-atm-vc)# class users Router(config-if-atm-vc)# exit Router(config-if)# exit Router(config)# vc-class atm users Router(config-vc-class)# encapsulation aal5snap Router(config-vc-class)# protocol pppoe Router(config-vc-class)# ^z
Step 1 Enter the show vpdn command from privileged EXEC mode. This output shows PPPoE session information. Confirm that the virtual-access interface status (VASt) is up.
Router# show vpdn PPPOE Tunnel and Session Session count: 1 PPPoE Session Information SID RemMAC LocMAC Intf VASt OIntf VC 1 0010.54db.bc38 0050.7327.5dc3 Vi1 UP AT0/0/0 0/40
Step 2 Enter the show atm pvc command from interface configuration mode. The last line of the output, "PPPOE enabled," confirms that PPPoE is enabled on this VC.
Router# show atm pvc 0/40 ATM0/0/0.2: VCD: 1, VPI: 0, VCI: 40 UBR, PeakRate: 155000 AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0 OAM frequency: 0 second(s), OAM retry frequency: 1 second(s), OAM retry frequency: 1 second(s) OAM up retry count: 3, OAM down retry count: 5 OAM Loopback status: OAM Disabled OAM VC state: Not Managed ILMI VC state: Not Managed InARP frequency: 15 minutes(s) InPkts: 100, OutPkts: 51, InBytes: 4692, OutBytes: 2294 InPRoc: 48, OutPRoc: 51, Broadcasts: 0 InFast: 0, OutFast: 0, InAS: 52, OutAS: 0 OAM cells received: 0 F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0 F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0 OAM cells sent: 0 F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0 F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0 OAM cell drops: 0 Status: UP
PPPOE enabled.
The following common routing and bridging protocols are detailed in the examples in this section:
For more information about routing and bridging, refer to the Cisco IOS Network Protocols Configuration Guide, Part 1 and the Bridging and IBM Networking Configuration Guide.
The Cisco 6400 NRP also offers routed bridging, which encapsulates bridged traffic in RFC 1483 routed packets. ATM routed bridging takes advantage of the characteristics of a stub LAN topology commonly used for digital subscriber line (DSL) access. See the "Configuring ATM Routed Bridging" section for routed bridging configuration tasks.
To configure an interface or subinterface for routing or bridging, perform the following tasks starting in global configuration mode:
| Step | Command | Description | ||
|---|---|---|---|---|
| interface atm 0/0/0 [.subinterface-number {multipoint | point-to-point}] | Specify the ATM interface and optional subinterface. | ||
| pvc [name] vpi/vci | Configure a new ATM PVC by assigning a name (optional) and VPI/VCI numbers. | ||
| encapsulation aal5snap1 | Configure AAL5 with SNAP encapsulation. | ||
| protocol protocol [protocol-address | inarp] [[no] broadcast] | Map a protocol address to the PVC. |
| 1AAL5 with SNAP encapsulation is defined by default for all PVCs. This command must be used to override a different encapsulation type at the interface or subinterface level. |
The following example shows how to configure RFC 1483 bridging on a multipoint interface. Arrows indicate subscriber bridging steps:
Router(config)# interface atm 0/0/0.10 multipoint Router(config-if)# no ip address Router(config-if)# bridge-group 1 Router(config-if)# pvc 1 32 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# protocol bridge broadcast Router(config-if-atm-vc)# exit Router(config-if)# pvc 1 33 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# protocol bridge broadcast Router(config-if-atm-vc)# exit Router(config-if)# exit Router(config)# bridge 1 protocol ieee
Router(config)# bridge 1 subscriber-policy 5
Router(config)# subscriber-policy 5 no ipx permit
The following example shows how to configure RFC1483 bridging on a point-to-point interface. Arrows indicate integrated routing and bridging steps:
Router(config)# interface atm 0/0/0.20 point-to-point Router(config-if)# no ip address Router(config-if)# bridge-group 2 Router(config-if)# pvc 2 32 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# protocol bridge broadcast Router(config-if-atm-vc)# exit Router(config-if)# exit Router(config)# interface atm 0/0/0.21 point-to-point Router(config-if)# no ip address Router(config-if)# bridge-group 2 Router(config-if)# pvc 2 33 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# protocol bridge broadcast Router(config-if-atm-vc)# exit Router(config-if)# exit
Router(config)# bridge irb
Router(config)# interface bvi 2
Router(config-if)# ip address 172.26.13.49 Router(config-if)# exit Router(config)# bridge 2 protocol ieee
Router(config)# bridge 2 route ip
Router(config)# bridge 2 bridge ipx
The following example shows how to configure RFC 1483 IP routing. When configuring IP on a PVC, you must either enable inverse ARP (InARP) or enter a static map:
Router(config)# interface atm 0/0/0.40 multipoint
Router(config-if)# ip address 172.25.210.97 255.255.0.0 Router(config-if)# pvc 4 32 Router(config-if-atm-vc)# encapsulation aal5snap
Router(config-if-atm-vc)# protocol ip inarp broadcast Router(config-if-atm-vc)# exit Router(config-if)# pvc 4 33 Router(config-if-atm-vc)# encapsulation aal5snap
Router(config-if-atm-vc)# protocol ip 10.3.45.156 broadcast Router(config-if-atm-vc)# exit Router(config-if)# exit Router(config)# interface atm 0/0/0.41 point-to-point
Router(config-if)# ip unnumbered fastethernet 0/0/0 Router(config-if)# pvc 4 34 Router(config-if-atm-vc)# encapsulation aal5snap
Router(config-if-atm-vc)# protocol ip inarp broadcast Router(config-if-atm-vc)# exit Router(config-if)# exit
| Step | Command | Description | ||
|---|---|---|---|---|
| interface atm 0/0/0.subinterface point-to-point | Specify an ATM point-to-point subinterface. | ||
| Enable ATM routed bridging for IP. | |||
| ip address ip-address mask [secondary] | Provide an IP address on the same subnetwork as the remote network. |
Only the specified network layer (IP) will be routed. Any remaining protocols can be passed on to bridging or other protocols. In this manner, ATM routed bridging can be used to route IP while other protocols (such as IPX) are bridged normally.
The following example shows how to configure ATM route-bridging. Note that ATM routed bridging will only work on a point-to-point interface.
Router(config)# interface atm 0/0/0.30 point-to-point
Router(config-if)# ip address 172.22.46.91 255.255.0.0
Router(config-if)# atm route-bridge ip Router(config-if)# pvc 3 32 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# protocol bridge broadcast Router(config-if-atm-vc)# exit Router(config-if)# exit
The following example shows how to configure concurrent ATM route-bridging and RFC1483 bridging.
Router(config)# interface atm 0/0/0.30 point-to-point
Router(config-if)# ip address 172.22.46.91 255.255.0.0 Router(config-if)# bridge-group 3
Router(config-if)# atm route-bridge ip Router(config-if)# pvc 3 32 Router(config-if-atm-vc)# encapsulation aal5snap Router(config-if-atm-vc)# protocol bridge broadcast Router(config-if-atm-vc)# exit Router(config-if)# exit Router(config)# bridge 3 protocol ieee
Posted: Mon Nov 15 12:45:17 PST 1999
Copyright 1989-1999©Cisco Systems Inc.