domingo, 17 de marzo de 2013

3.6.1


 

hostname HQ
no ip domain-lookup
enable password cisco
banner motd #Welcome to Router HQ#
line console 0
password cisco
login
line vty 0
password cisco
login
int s0/0/0
ip add 10.0.0.1 255.255.255.252
clock rate 64000
no shutdown
int s0/0/1
ip add 10.0.0.5 255.255.255.252
no shutdown
clock rate 64000
int s0/1/0
ip add 10.0.0.9 255.255.255.252
no shutdown
clock rate 64000
int s0/1/1
ip add 209.165.201.2 255.255.255.252
no shutdown
clock rate 64000
int fa0/0
ip add 192.168.0.129 255.255.255.224
no shutdown
int fa0/1
ip add 192.168.0.161 255.255.255.224
no shutdown
ip route 192.168.1.0 255.255.255.0 s0/0/0
ip route 0.0.0.0 0.0.0.0 s0/1/1
end
copy running-config startup-config
startup-config
reload
y




hostname B1
no ip domain-lookup
enable password cisco
banner motd #Welcome to Router B1#
line console 0
password cisco
login
line vty 0
password cisco
login
int s0/0/0
ip add 10.0.0.2 255.255.255.252
clock rate 64000
no shutdown
int fa0/0
ip add 192.168.1.1 255.255.255.192
no shutdown
int fa0/1
ip add 192.168.1.65 255.255.255.192
no shutdown
int fa1/0
ip add 192.168.1.129 255.255.255.192
no shutdown
int fa1/1
ip add 192.168.1.193 255.255.255.192
no shutdown
ip route 0.0.0.0 0.0.0.0 s0/0/0
end
copy running-config startup-config
startup-config
reload
y





hostname B2
no ip domain-lookup
enable password cisco
banner motd #Welcome to Router B2#
line console 0
password cisco
login
line vty 0
password cisco
login
int s0/0/0
ip add 10.0.0.6 255.255.255.252
clock rate 64000
no shutdown
int fa0/0
ip add 172.16.0.1 255.255.252.0
no shutdown
int fa0/1
ip add 172.16.4.1 255.255.252.0
no shutdown
int fa1/0
ip add 172.16.8.1 255.255.252.0
no shutdown
int fa1/1
ip add 172.16.12.1 255.255.252.0
no shutdown
ip route 0.0.0.0 0.0.0.0 s0/0/0
end
copy running-config startup-config
startup-config
reload
y



hostname B3
no ip domain-lookup
enable password cisco
banner motd #Welcome to Router B3#
line console 0
password cisco
login
line vty 0
password cisco
login
int s0/0/0
ip add 10.0.0.10 255.255.255.252
clock rate 64000
no shutdown
int fa0/0
ip add 172.20.0.1 255.255.224.0
no shutdown
int fa0/1
ip add 172.20.32.1 255.255.224.0
no shutdown
int fa1/0
ip add 172.20.64.1 255.255.224.0
no shutdown
int fa1/1
ip add 172.20.96.1 255.255.224.0
no shutdown
ip route 0.0.0.0 0.0.0.0 s0/0/0
end
copy running-config startup-config
startup-config
reload
y

hostname ISP
no ip domain-lookup
enable password cisco
banner motd #Welcome to Router ISP#
line console 0
password cisco
login
line vty 0
password cisco
login
int s0/0/0
ip add 209.165.201.1 255.255.255.252
clock rate 64000
no shutdown
int fa0/0
ip add 209.165.200.225 255.255.255.252
no shutdown
ip route 192.168.1.0 255.255.255.0 s0/0/0
ip route 10.0.0.0 255.255.255.252 s0/0/0
ip route 10.0.0.4 255.255.255.252 s0/0/0
ip route 10.0.0.8 255.255.255.252 s0/0/0
end
copy running-config startup-config
startup-config
reload

domingo, 10 de marzo de 2013

6.4.1



Task 1: Apply Basic Router Configurations
Step 1: Configure basic commands.

Using the information in the topology diagram and addressing table, configure the basic device configurations on R1, R2, and R3. Hostnames are configured for you.
R1
R1>en
R1#conf t
R1(config)#line con 0
R1(config-line)#password cisco
R1(config-line)#login
R1(config-line)#exit
R1(config)#line vty 0 4
R1(config-line)#password cisco
R1(config-line)#login
R1(config-line)#exit
R1(config)#banner motd "Access to Router R1"
R1(config)#no ip domain-lookup
R1(config)#int s0/0/0
R1(config-if)#description line to cloud-PT
R1(config-if)#exit
R1(config)#int f0/0
R1(config-if)#desc
R1(config-if)#description fastethernet LAN
R1(config-if)#exit
R1(config-if)#
R2
R2>en
R2#conf t
R2(config)#line con 0
R2(config-line)#password cisco
R2(config-line)#login
R2(config-line)#exit
R2(config)#line vty 0 4
R2(config-line)#password cisco
R2(config-line)#login
R2(config-line)#exit
R2(config)#banner motd "Access to Router R2"
R2(config)#no ip domain-lookup
R2(config)#int s0/0/0
R2(config-if)#description line to cloud-PT
R2(config-if)#exit
R2(config)#int s0/1/0
R2(config-if)#description line to ISP
R2(config-if)#exit
R2(config)#int f0/0
R2(config-if)#description line to LAN
R2(config-if)#exit
R2(config)#
R3
R3>en
R3#conf t
R3(config)#line con 0
R3(config-line)#password cisco
R3(config-line)#login
R3(config-line)#exit
R3(config)#line vty 0 4
R3(config-line)#password cisco
R3(config-line)#login
R3(config-line)#exit
R3(config)#banner motd "Access to Router R3"
R3(config)#no ip domain-lookup
R3(config)#int s0/0/0
R3(config-if)#description line to cloud-PT
R3(config-if)#exit
R3(config)#int f0/0
R3(config-if)#description line to LAN
R3(config-if)#exit
R3(config)#
Task 2: Configure Dynamic and Default Routing
Step 1. Configure default routing.

R2 needs a default route. Use the exit-interface argument in the default route configuration.
R2(config)#ip route 0.0.0.0 0.0.0.0 s0/1/0
Step 2. Configure dynamic routing.
Configure RIPv2 on R1, R2, and R3 for all available networks. R2 needs to pass its default network configuration to the other routers. Also, be sure to use the passive-interface command on all active interfaces not used for routing.
R1
R1(config)#router rip
R1(config-router)#version 2
R1(config-router)#network 10.1.1.0
R1(config-router)#network 192.168.10.0
R1(config-router)#passive-interface f0/1
R1(config-router)#no auto-summary
R1(config-router)#exit
R1(config)#
R2
R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#network 10.1.1.0
R2(config-router)#network 192.168.20.0
R2(config-router)#default-information originate
R2(config-router)#passive-interface s0/1/0
R2(config-router)#passive-interface f0/1
R2(config-router)#no auto-summary
R2(config-router)#exit
R2(config)#
R3
R3(config)#router rip
R3(config-router)#version 2
R3(config-router)#network 10.1.1.0
R3(config-router)#network 192.168.30.0
R3(config-router)#passive-interface f0/1
R3(config-router)#no auto-summary
R3(config-router)#exit
R3(config)#
Task 5: Apply ACL Policies
Step 1. Create and apply security policy number 1.

Implement the following ACL rules using ACL number 101:
Allow hosts on the 192.168.30.0/24 network web access to any destination.
Allow hosts on the 192.168.30.0/24 network ping access to any destination.
Deny any other access originating from the network.

R3
R3(config)#access-list 101 permit tcp 192.168.30.0 0.0.0.255 any eq www
R3(config)#access-list 101 permit icmp 192.168.30.0 0.0.0.255 any
R3(config)#access-list 101 deny ip any any
R3(config)#int fa0/1
R3(config-if)#ip access-group 101 in
R3(config-if)#exit
R3(config)#
Step 2. Create and apply security policy number 2.
Because ISP represents connectivity to the Internet, configure a named ACL called FIREWALL in the following order:
Allow TW-DSL web access to the Intranet server.
Allow TW-Cable web access to the Intranet server.
Allow only inbound ping replies from ISP and any source beyond ISP.
Allow only established TCP sessions from ISP and any source beyond ISP.
Explicitly block all other inbound access from ISP and any source beyond ISP.

R2
R2(config)#ip access-list extended FIREWALL
R2(config-ext-nacl)#permit tcp host 192.168.1.10 host 192.168.20.254 eq www
R2(config-ext-nacl)#permit tcp host 192.168.2.10 host 192.168.20.254 eq www
R2(config-ext-nacl)#permit icmp any any echo-reply
R2(config-ext-nacl)#permit tcp any any established
R2(config-ext-nacl)#deny ip any any
R2(config-ext-nacl)#int s0/1/0
R2(config-if)#ip access-group FIREWALL in
R2(config-if)#exit
R2(config)#

domingo, 27 de enero de 2013

2.17 Resolucion de problemas de una unidad serial


¿Cual es el ultimo router que responde al tracert?
-R1 hay comunicación con la interfaz fa 0/0 pero no con la S0/0/0.

¿Cuales son algunas posibles razones por la que puede faltar un enlace serial?
-Una interfaz serial puede dar fallo si esta no esta activa, si el cable esta conectado a una interfaz 
erronea si la velocidad del reloj no es la misma en las dos extensiones del serial.

Resumen de resultado:
Problema 1:R1 tiene configurado la encapsulación PPP y en realidad se necesita la HDLC
Solución:Configurar la intefaz serial 0/0/0 de R1 en HDLC.
 Problema 2:R2 interfaz s 0/0/1 no tiene activado el reloj.
Solucion:Activar la señal de reloj y configurarla a 64000 como en R3
Problema 3:R3 interfaz serial 0/0/0 no tiene el cable conectado.
Solución:Activamos la serial 0/0/1 

Pasos:
Por medio del telnet se accede al ultimo ruter que responde al comando, desde la PC. El router que responde es R1.
Se utilizan unos comandos para verificar la falla de la red; 
-Show ip interface brief: En este no se encuentra ningun problema.
-Sho interface serial 0/0/0: Se encuentra el error del PPP en el cual se soluciona con el comando interface serial 0/0/0 encapsulation HDLC
En R2 con el comando serial 0/0/1 encontramos el error del reloj en el que se inserta mediante el clock rate 64000
El siguiente error se encuentra en R3 al hacer telnet de Pc3 a R3 y por medio de sho controller serial 0/0/0 se observa que no habia cable conectado en el serial  

domingo, 20 de enero de 2013

CCNA4 - 1.4.1



1-CONFIGURAR LAS INTERFACES DE LAS VLAN(10,20,30)

S1(config)#interface vlan10
S1(config-if)#ip address 192.168.10.2 255.255.255.0
S2(config)#interface vlan20
S2(config-if)#ip address 192.168.20.2 255.255.255.0
S3(config)#interface vlan30                                                                                                                                         S3(config-if)#i p address 192.168.30.2 255.255.255.0
2-VTP
S1(config)#vtp mode server
Setting device to VTP SERVER mode
S1(config)#vtp domain cisco
Changing VTP domain name from NULL to cisco
S1(config)#vtp password cisco
Setting device VLAN database password to cisco
S2(config)#vtp mode client
Setting device to VTP CLIENT mode
S2(config)#vtp domain cisco
Changing VTP domain name from NULL to cisco
S2(config)#vtp password cisco
Setting device VLAN database password to cisco

S3(config)#vtp mode client Setting device to VTP CLIENT mode
S3(config)#vtp domain cisco
Changing VTP domain name from NULL to cisco
S3(config)#vtp password cisco
Setting device VLAN database password to cisco
3-CONFIGURAR S1 VLANS
S1(config)# vlan 10,12,13,20,30
4-TRUNK
S1:
interface FastEthernet0/1
switchport trunk allowed vlan 10,12,13
switchport mode trunk
!
interface FastEthernet0/2
switchport access vlan 10
switchport mode access
!
interface GigabitEthernet0/1
switchport trunk allowed vlan 1,12
switchport mode trunk
!
interface GigabitEthernet0/2
switchport trunk allowed vlan 1,13
switchport mode trunk
!
S2:
interface FastEthernet0/1
switchport trunk allowed vlan 12,20
switchport mode trunk
!
interface FastEthernet0/2
switchport access vlan 20
switchport mode access
!
interface GigabitEthernet0/1
switchport trunk allowed vlan 12
switchport mode trunk
!
S3:
interface FastEthernet0/1
switchport trunk allowed vlan 13,30
switchport mode trunk
!
interface FastEthernet0/2
switchport access vlan 30
switchport mode access
!
interface GigabitEthernet0/1
switchport trunk allowed vlan 13
switchport mode trunk