0.7 CAPITULO 1 - Caracterización de las Microempresas objeto de estudio
0.7.4 PERCEPCIÓN DEL ENTORNO
Lab 7 Setup
This lab is intended to be used with online rack access. Connect to the terminal server for the online rack, and complete the configuration tasks as detailed below.
Configuration Tasks :: Detailed Solutions
1. The link between R3 and R4 should be using the HDLC encapsulation. Check that you can ping from R3 to R4.
The link has been pre-configured with PPP and we have to configure the HDLC encapsulation instead.
On R3, configure the following:
R3(config-if)#int s4/3
R3(config-if)#encapsulation hdlc
NOTE
Load the initial configuration files before starting to work on the tasks.
91 | P a g e Version 5.2C On R4, configure the following:
R4(config)#int s4/0
R4(config-if)#encapsulation hdlc
The ping from R3 to R4 is working:
R3#ping 10.1.34.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.34.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/9 ms
2. The link between R3 and R5 should be using the PPP encapsulation. Turn on the CHAP authentication with the password of “Password35”. Check that you can ping from R3 to R5.
On R3, configure the following:
R3(config)#username R5CHAP1 password Password35 R3(config)#int s4/0
R3(config-if)#encapsulation ppp R3(config-if)#ppp authentication chap R3(config-if)#ppp chap hostname R3CHAP1
On R5, configure the following:
R5(config)#username R3CHAP1 password Password35 R5(config)#int s4/0
R5(config-if)#encapsulation ppp R5(config-if)#ppp authentication chap R5(config-if)#ppp chap hostname R5CHAP1
Let’s check that we can still ping from R5 to R3.
R5#ping 10.1.35.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.35.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/9 ms
Version 5.2C 92 | P a g e 3. The link between R3 and R6 should be using the PPP encapsulation. Turn on the PAP
authentication with the password of “Password361”. If the PAP authentication is unsuccessful, CHAP authentication has to kick in with a password of “Password362”. Check that you can ping from R3 to R6.
Let’s check that we can still ping from R6 to R3.
R6#ping 10.1.36.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.36.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/9 ms
In order to test that CHAP is working when PAP is not working, we can use the interface-level command ppp pap refuse on both sides (R3 and R6).
4. Configure PPPoE between the R6 and the R2 routers. R6 is the server side and R2 is the client side. On the server side, a BBA is called “iPexpertgroup”. The IP pool is called” iPexpertpool” and the range is from 10.1.26.10 to 10.1.26.20. The virtual-template number should use ID 23 and the IP address configured on the virtual template is 10.1.26.6 255.255.255.0.
93 | P a g e Version 5.2C On the server side R6, configure the following:
R6(config)#bba-group pppoe iPexpertgroup R6(config-bba-group)#virtual-template 23 R6(config-bba-group)#interface E0/0 R6(config-if)#no ip address
R6(config-if)#pppoe enable group iPexpertgroup R6(config-if)#interface virtual-template 23 R6(config-if)#ip address 10.1.26.6 255.255.255.0
R6(config-if)#peer default ip address pool iPexpertpool
R6(config-if)#ip local pool iPexpertpool 10.1.26.10 10.1.26.20
5. Limit the number of sessions established (per client MAC address) to 3.
This task should be configured in the broadband aggregation (BBA) group.
On the server side R6, configure the following:
R6(config)#bba-group pppoe iPexpertgroup R6(config-bba-group)#sessions per-mac limit 3
6. On the client side, use the ID 26 for both the dialer interface and the dialer-pool-number interface. Check that you can ping from R6 to R2.
On the client side R2, configure the following:
R2(config)#interface E0/1 R2(config-if)#no ip address R2(config-if)#pppoe enable
R2(config-if)#pppoe-client dial-pool-number 26 R2(config-if)#interface dialer 26
R2(config-if)#ip address negotiated R2(config-if)#encapsulation ppp R2(config-if)#dialer pool 26
The client side has been assigned the IP address 10.1.26.10 by the server.
Version 5.2C 94 | P a g e
R2#sh int dialer 26
Dialer26 is up, line protocol is up (spoofing) Hardware is Unknown
Internet address is 10.1.26.10/32
MTU 1500 bytes, BW 56 Kbit/sec, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, LCP Closed, loopback not set Keepalive set (10 sec)
DTR is pulsed for 1 seconds on reset Interface is bound to Vi2
Last input never, output never, output hang never Last clearing of "show interface" counters 00:08:17
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 5 packets input, 68 bytes reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, LCP Open
Stopped: CDPCP Open: IPCP
PPPoE vaccess, cloned from Dialer26 Vaccess status 0x44, loopback not set Keepalive set (10 sec)
Interface is bound to Di26 (Encapsulation PPP) Last input 00:00:00, output never, output hang never Last clearing of "show interface" counters 00:00:43
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 11 packets input, 148 bytes, 0 no buffer
95 | P a g e Version 5.2C
Received 0 broadcasts (0 IP multicasts) 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 12 packets output, 142 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets 0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out 0 carrier transitions
I can ping from R6 to R2 using PPPoE.
R6#ping 10.1.26.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.26.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms
7. Make sure that unnecessary fragmentation is avoided.
The PPP header adds 8 bytes of overhead to each frame. As the default Ethernet MTU is 1500 bytes, it is recommended to lower our MTU on the dialer interface to 1492 to avoid unnecessary fragmentation.
On the client side R2, configure the following:
R2(config)#interface dialer 26 R2(config-if)#mtu 1492
8. The client R2 should authenticate when connecting on the server. Create a local account username called R2 with the password of “Password26”.
On the R6, configure the following:
R6(config)#username R2 password Password26 R6(config)#interface virtual-template 23 R6(config-if)#ppp authentication chap callin
On R2, configure the following:
Version 5.2C 96 | P a g e
R2(config)#interface dialer 26
R2(config-if)#ppp chap password Password26
Let’s check that the ping between R6 and R2 using PPPoE is working.
R6#ping 10.1.26.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.26.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms
9. Bundle with PPP multilink the two serial connections between R6 and R9. Use a group ID of 69.
On R6 and R9, configure the following:
RX(config)#int multilink 69
RX(config-if)#interface serial 3/0 RX(config-if)#encapsulation ppp RX(config-if)#ppp multilink group 69 RX(config-if)#no shut
RX(config-if)#interface serial 3/1 RX(config-if)#encapsulation ppp RX(config-if)#ppp multilink group 69 RX(config-if)#no shut
10. Configure the IP address of 10.1.69.6/24 on the R6 PPP multilink69. Configure the IP address of 10.1.69.9/24 on the R9 PPP multilink69. Check that you can ping from R6 to R9.
On R6, configure the following:
R6(config-if)#interface multilink 69
R6(config-if)#ip address 10.1.69.6 255.255.255.0 R6(config-if)#no shut
On R9, configure the following:
R9(config-if)#interface multilink 69
R9(config-if)#ip address 10.1.69.9 255.255.255.0 R9(config-if)#no shut
97 | P a g e Version 5.2C I can ping over the multilink circuit:
R6#ping 10.1.69.9
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.69.9, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/9 ms
11. Ensure that it is checked on the PPP multilink interfaces that all the fragments of an IP datagram are received on the virtual interfaces before forwarding them.
On R6 and R9, configure the following:
RX(config)#int multilink69
RX(config-if)#ip virtual-reassembly
12. There will be voice traffic running over the multilink PPP connection. Ensure that a small voice packet is delayed a maximum of 20 ms because of the transmission of a big data packet.
On R6 and R9, configure the following:
RX(config)#int multilink69
RX(config-if)#ppp multilink fragment delay 20 RX(config-if)#ppp multilink interleave
13. Reserve 1 Mbps in a special queue for real-time packet flows designated to the UDP port starting 32768 and ending 32867.
On R6 and R9, configure the following:
RX(config-if)#class-map match-all RTP RX(config-cmap)#match ip rtp 32768 100 RX(config-cmap)#policy-map RTP
RX(config-pmap)#class RTP RX(config-pmap-c)#priority 1000 RX(config-pmap-c)#int multilink69 RX(config-if)#ppp multilink multiclass RX(config-if)#service-policy output RTP
Version 5.2C 98 | P a g e
Helpful Verification Commands
Show ppp interface
Show pppoe summary
Show pppoe statistics
Show vpdn
Show vpdn session all
Technical Verification and Support
To verify your configurations please ensure that you have downloaded the latest “final configurations” from within the iPexpert Member’s Area.
For instructor and developer support, please be sure to submit questions through our interactive support community that’s accessible from the Member’s Area.
This concludes Lab 7 of iPexpert’s CCIE Routing & Switching DSG Volume 1, Section 1 Copyright© iPexpert. All Rights Reserved.
99 | P a g e Version 5.2C
Section 2: Layer 3 Technologies
Version 5.2C 100 | P a g e
Lab 8: Configure and Troubleshoot Basic IP Routing :: Detailed Solutions
Technologies Covered
Static route
Traffic engineering
Floating static route
Object tracking
PBR
GRE
Detailed Solution Guide
This part of the material is designed to provide our students with the exact commands to use, when to use them, and also the various show commands that will allow you to understand what you're looking for. In addition, the instructor has provided some detail as to why the various solutions have been used versus another potential command set that would have accomplished the same outcome.
101 | P a g e Version 5.2C
iPexpert’s Recommended Reading Material
Policy-based Routing:
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_pi/configuration/15-mt/iri-15-mt-book/iri-pbr.html
Basic IP Routing:
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_pi/configuration/15-mt/iri-15-mt-book/iri-iprouting.html
Configuring a GRE Tunnel:
https://supportforums.cisco.com/document/13576/how-configure-gre-tunnel
How GRE Keepalives Work:
http://www.cisco.com/c/en/us/support/docs/ip/generic-routing-encapsulation-gre/118370-technote-gre-00.html
iPexpert’s Recommended Video Training
iPexpert’s Video on Demand training library contains a wealth of videos pertaining to the CCIE Routing & Switching lab exam. We recommend watching the following learning videos, which cover the topics seen in this lab scenario.
Video Title: IP Routing
Video Title: Policy-based Routing
Video Title: Tunneling & GRE
Video Title: GRE tunnels
Video Title: Service Level Agreement (SLA) and Object Tracking
Topology Details
Logically connect and configure your network as displayed in the drawing below. You may also refer to the diagram located within your configuration files for topology information.
The topology used in the lab will be the following:
Version 5.2C 102 | P a g e