Home > Articles > Cisco > CCNP Routing and Switching

  • Print
  • + Share This
This chapter is from the book

Scenarios

This section presents several examples of DSL access configurations. The scenarios cover the configuration for a DSLAM, a Cisco 6400 UAC NSP, a Cisco 6400 UAC NRP, and a DSL CPE - Cisco 827.

Scenario 8-1: Configuring IRB over DSL

In this scenario, you will configure the DSL solution to support data transport using IRB. When completed, the Cisco 827 should train up with the DSLAM, and you should be able to ping and access all normal network services from a client PC attached to the DSL CPE modem. Figure 8-9 illustrates how these devices are interconnected.

Figure 9Figure 8-9 IRB Lab Scenario

In Example 8-13, the PVC is mapped from the Cisco 827 DSL connection (ATM1/1) to the DSLAM trunking port (ATM0/1).

Example 8-13 ATM PVC Configuration for the Cisco 6160 DSLAM

interface ATM1/1
 description IRB Architecture
 no ip address
 no atm ilmi-keepalive
 atm pvc 1 51 interface ATM0/1 1 51

In Example 8-14, the PVC is configured from the DSLAM to the NSP and NRP. Interface ATM8/0/0 is the network line card, and interface ATM1/0/0 is the NRP.

Example 8-14 ATM PVC Configuration for the NSP

interface ATM8/0/0
 description OC3 connection to lab-6160
 no ip address
 no ip directed-broadcast
 no atm ilmi-keepalive
 atm pvc 1 51 interface ATM1/0/0 1 51

A bridge group is configured for IP, and a BVI is created for IRB. The BVI becomes the default gateway for the remote device attached to the CPE equipment (which will be in subnet 10.1.121.0/24). A subinterface is created for a PVC to the NSP. (See the NSP configuration. The NSP maps this PVC to another PVC from the DSLAM, which maps to the subscriber PVC.) In this case, the 1/51 PVC is mapped across the NSP to the 6160. The subinterface is also put in the bridge group. Example 8-15 shows the IRB configuration for the NRP.

Example 8-15 IRB Configuration for the NRP

bridge irb
!
interface BVI1
ip address 10.1.121.1 255.255.255.0
no ip directed-broadcast
!
bridge 1 protocol ieee
 bridge 1 route ip
!
interface ATM0/0/0
no ip address
no ip directed-broadcast
!
interface ATM0/0/0.51 point-to-point

description IRB Configuration
no ip directed-broadcast
pvc 1/51
encapsulation aal5snap
!
bridge-group 1

Example 8-16 shows the bridging configuration for the DSL CPE.

Example 8-16 RFC 1483 Bridging Configuration for the Cisco 827

hostname lab-827A
!
ip subnet-zero
no ip routing
!
interface Ethernet0
 ip address 10.1.121.2 255.255.255.0
 no ip directed-broadcast
 no ip mroute-cache
 bridge-group 1
!
interface atm0
 mac-address 0001.96a4.8fae  <--- MAC Address from Ethernet 0
 ip address 10.1.121.2 255.255.255.0
 no ip directed-broadcast
 no ip mroute-cache
 no atm ilmi-keepalive
 pvc 1/51
 encapsulation aal5snap
 !
 bundle-enable
 bridge-group 1
 hold-queue 224 in
!
ip classless
no ip http server
!
bridge 1 protocol ieee

Scenario 8-2: Configuring RBE over DSL

In this scenario, you will configure the DSL solution to support data transport using RBE. When completed, the Cisco 827 should train up with the DSLAM, and you should be able to ping and access all normal network services from a client PC attached to the DSL CPE modem. Figure 8-10 illustrates how these devices are interconnected.

Figure 10Figure 8-10 RBE Scenario

In Example 8-17, the PVC is mapped from the Cisco 827 DSL connection (ATM1/2) to the DSLAM trunking port (ATM0/1).

Example 8-17 ATM PVC Configuration for the Cisco 6160 DSLAM

interface ATM1/2
 description RBE Architecture
 no ip address
 no atm ilmi-keepalive
 atm pvc 1 52 interface ATM0/1 1 52

In Example 8-18, the PVC is configured from the DSLAM to the NSP and NRP. Interface ATM8/0/0 is the network line card, and interface ATM1/0/0 is the NRP.

Example 8-18 ATM PVC Configuration for the NSP

interface ATM8/0/0
 description OC3 connection to lab-6160
 no ip address
 no ip directed-broadcast
 no atm ilmi-keepalive
 atm pvc 1 52 interface ATM1/0/0 1 52

Example 8-19 shows the RBE configuration for the NRP. You saw the configuration steps in the previous section.

Example 8-19 RBE Configuration for the NRP

interface Loopback1
 ip address 10.1.121.1 255.255.255.0
 no ip directed-broadcast
!
interface ATM0/0/0
no ip address
no ip directed-broadcast

!
interface ATM0/0/0.52 point-to-point
 description RBE Configuration
 ip unnumbered Loopback1
 atm route-bridged ip
 pvc 1/52
 encapsulation aal5snap
!
ip route 10.1.121.2 255.255.255.255 ATM0/0/0.52

Example 8-20 shows the bridging configuration for the DSL CPE. As you can see, the CPE configuration is the same when you configure the IRB over DSL.

Example 8-20 RFC 1483 Bridging Configuration for the Cisco 827

hostname lab-827B
!
ip subnet-zero
no ip routing
!
interface Ethernet0
 ip address 10.1.121.2 255.255.255.0
 no ip directed-broadcast
 no ip mroute-cache
 bridge-group 1
!
interface atm0
 mac-address 0001.96a4.8fae
 ip address 10.1.121.2 255.255.255.0
 no ip directed-broadcast
 no ip mroute-cache
 no atm ilmi-keepalive
 pvc 1/52
 encapsulation aal5snap
 !
 bundle-enable
 bridge-group 1
 hold-queue 224 in
!
ip classless
no ip http server
!
bridge 1 protocol ieee

Scenario 8-3: Configuring PPPoA over DSL

In this scenario, you will configure the DSL solution to support data transport using PPPoA. When completed, the Cisco 827 should train up with the DSLAM, and you should be able to ping and access all normal network services from a client PC attached to the DSL CPE modem. Figure 8-11 illustrates how these devices are interconnected.

Figure 11Figure 8-11 PPPoA Lab Scenario

In Example 8-21, the PVC is mapped from the Cisco 827 DSL connection (ATM1/3) to the DSLAM trunking port (ATM0/1).

Example 8-21 ATM PVC Configuration for the Cisco 6160 DSLAM

interface ATM1/3
 description PPPoA Architecture
 no ip address
 no atm ilmi-keepalive
 atm pvc 1 53 interface ATM0/1 1 53

In Example 8-22, the PVC is configured from the DSLAM to the NSP and NRP. Interface ATM8/0/0 is the network line card, and interface ATM1/0/0 is the NRP.

Example 8-22 ATM PVC Configuration for the NSP

interface ATM8/0/0
 description OC3 connection to lab-6160
 no ip address
 no ip directed-broadcast
 no atm ilmi-keepalive
 atm pvc 1 53 interface ATM1/0/0 1 53

Example 8-23 shows the PPPoA configuration for the NRP.

Example 8-23 PPPoA Configuration for the NRP

username cisco password 0 cisco
!
interface ATM0/0/0
no ip address
no ip directed-broadcast
!
interface ATM0/0/0.53 point-to-point
 description PPPoA Configuration
 pvc 1/53

 encapsulation aal5mux ppp Virtual-Template1
 !
interface Virtual-Template1
 description PPPoA
 ip unnumbered Ethernet0/0/0
 peer default ip address pool ccnp
 ppp authentication chap pap

Example 8-24 shows the PPPoA configuration for the DSL CPE.

Example 8-24 PPPoA Configuration for the Cisco 827

hostname lab-827C
!
ip subnet-zero
!
interface Ethernet0
 ip address 10.0.0.1 255.255.255.0
 no ip directed-broadcast
 no ip mroute-cache
!
interface ATM0
 no ip address
 no ip directed-broadcast
 no ip mroute-cache
 no atm ilmi-keepalive
 pvc 1/53
 encapsulation aal5mux ppp dialer
 dialer pool-member 1
 !
!
interface Dialer1
 ip address negotiated
 no ip directed-broadcast
 encapsulation ppp
 dialer pool 1
 dialer-group 1
 ppp authentication chap callin
 ppp chap hostname cisco
 ppp chap password cisco
!
ip classless
!
dialer-list 1 protocol ip permit

When a PPP connection is made, a virtual interface is created, as shown in Example 8-25. The connection is authenticated with PAP/CHAP (using username "cisco" and password "cisco"). IP addresses are negotiated and handed out from the address pool named ccnp.

Example 8-25 Verifying the Virtual Interface

lab-6400NRP#show interface virtual-access 1
Virtual-Access1 is up, line protocol is up
 Hardware is Virtual Access interface
 Description: PPPoA
 Interface is unnumbered. Using address of Ethernet0/0/0 (10.1.1.190)
 MTU 1500 bytes, BW 100000 Kbit, DLY 100000 usec,
   reliability 255/255, txload 1/255, rxload 1/255
 Encapsulation PPP, loopback not set
 Keepalive set (10 sec)
 DTR is pulsed for 5 seconds on reset
 LCP Open
 Open: IPCP
 Bound to ATM0/0/0.53 VCD: 3, VPI: 1, VCI: 53
 Cloned from virtual-template: 1
 Last input 00:00:03, output never, output hang never
 Last clearing of "show interface" counters 14:05:57
 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
   10239 packets input, 141642 bytes, 0 no buffer
   Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
   0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
   21626 packets output, 852074 bytes, 0 underruns
   0 output errors, 0 collisions, 0 interface resets
   0 output buffer failures, 0 output buffers swapped out
   0 carrier transitions

Scenario 8-4: Configuring PPPoE over DSL

In this scenario, you will configure the DSL solution to support data transport using PPPoE. When completed, the Cisco 827 should train up with the DSLAM, and you should be able to ping and access all normal network services from a client PC attached to the DSL CPE modem. Figure 8-12 illustrates how these devices are interconnected.

Figure 12Figure 8-12 PPPoE Lab Scenario

In Example 8-26, the PVC is mapped from the Cisco 827 DSL connection (ATM1/4) to the DSLAM trunking port (ATM0/1).

Example 8-26 ATM PVC Configuration for the Cisco 6160 DSLAM

interface ATM1/4
 description PPPoE Architecture
 no ip address
 no atm ilmi-keepalive
 atm pvc 1 54 interface ATM0/1 1 54

In Example 8-27, the PVC is configured from the DSLAM to the NSP and NRP. Interface ATM8/0/0 is the network line card, and interface ATM1/0/0 is the NRP.

Example 8-27 ATM PVC Configuration for the NSP

interface ATM8/0/0
 description OC3 connection to lab-6160
 no ip address
 no ip directed-broadcast
 no atm ilmi-keepalive
 atm pvc 1 54 interface ATM1/0/0 1 54

Example 8-28 shows the PPPoE configuration for the NRP.

Example 8-28 PPPoE Configuration for the NRP

username cisco password 0 cisco
!
vpdn enable
!
vpdn-group 1
 accept-dialin
 protocol pppoe
 virtual-template 1
interface ATM0/0/0
no ip address
no ip directed-broadcast
!
interface ATM0/0/0.54 point-to-point
 description LAB PPPoE Configuration
 pvc 1/54
 encapsulation aal5snap
 protocol pppoe
 !
interface Virtual-Template1
 description PPPoE
 ip unnumbered Ethernet0/0/0
 ip mtu 1492
 peer default ip address pool ccnp
 ppp authentication chap pap

For PPPoE over DSL, the DSL CPE is also configured for pure RFC 1483 bridging, as shown in Example 8-29.

Example 8-29 RFC 1483 Bridging Configuration for the Cisco 827

hostname lab-827D
!
ip subnet-zero
no ip routing
!
interface Ethernet0
 no ip address
 no ip directed-broadcast
 no ip mroute-cache
 bridge-group 1
!
interface atm0
 mac-address 0001.96a4.8fae
 ip address 10.1.121.2 255.255.255.0
 no ip directed-broadcast
 no ip mroute-cache
 no atm ilmi-keepalive
 pvc 1/52
 encapsulation aal5snap
 !
 bundle-enable
 bridge-group 1
 hold-queue 224 in
!
ip classless
no ip http server
!
bridge 1 protocol ieee

When a PPP connection is made, a virtual interface is created, as shown in Example 8-30. The connection is authenticated with PAP/CHAP (using username "cisco" and password "cisco"). IP addresses are negotiated and handed out from the address pool named ccnp.

Example 8-30 Verifying the Virtual Interface

lab-6400NRP#show int Virtual-Access3
Virtual-Access3 is up, line protocol is up
 Hardware is Virtual Access interface
 Description: PPPoE
 Interface is unnumbered. Using address of Ethernet0/0/0 (10.1.1.190)
 MTU 1492 bytes, BW 100000 Kbit, DLY 100000 usec,
   reliability 255/255, txload 1/255, rxload 1/255
 Encapsulation PPP, loopback not set
 Keepalive set (10 sec)
 DTR is pulsed for 5 seconds on reset
 LCP Open
 Open: IPCP

 Bound to ATM0/0/0.54 VCD: 4, VPI: 1, VCI: 54
 Cloned from virtual-template: 1
 Last input 00:00:04, output never, output hang never
 Last clearing of "show interface" counters 00:01:34
 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
   40 packets input, 2923 bytes, 0 no buffer
   Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
   0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
   78 packets output, 6071 bytes, 0 underruns
   0 output errors, 0 collisions, 0 interface resets
   0 output buffer failures, 0 output buffers swapped out
   0 carrier transitions
  • + Share This
  • 🔖 Save To Your Account