From: Julian Rodriguez (jumaroyu@gmail.com)
Date: Sat Aug 11 2007 - 09:53:01 ART
I just don't understand how, the only protocol enabled between SW2 and BB2
is RIP at this time. Check it out:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!! IECWB-RSv4 BB2 !!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! This router is configured to allow telnet
!! for verification purposes. In the real lab
!! you will not have access to the BB routers.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
version 12.2
no service timestamps debug uptime
no service timestamps log uptime
no service password-encryption
!
hostname BB2
!
logging queue-limit 100
enable secret cisco
!
clock timezone PST -8
clock summer-time PDT recurring
ip subnet-zero
no ip domain lookup
!
ipv6 unicast-routing
frame-relay switching
!
key chain RIP
key 1
key-string CISCO
!
!
!
interface Loopback0
ip address 220.20.3.1 255.255.255.0
ipv6 address 2001:220:20:3::1/64
ipv6 rip RIPng enable
!
interface Loopback1
ip address 222.22.2.1 255.255.255.0
ipv6 address 2001:222:22:2::1/64
ipv6 rip RIPng enable
!
interface Loopback3
ip address 205.90.31.1 255.255.255.0
ipv6 address 2001:205:90:31::1/64
ipv6 rip RIPng enable
!
interface Loopback100
ip address 1.1.1.1 255.255.255.255
!
interface Loopback51515151
ip address 51.51.51.51 255.255.255.255
ipv6 address 2001:51:51:51::51/64
!
interface Ethernet0
description Ethernet to SW2 Fa0/24
ip address 192.10.1.254 255.255.255.0
ip rip authentication mode md5
ip rip authentication key-chain RIP
ipv6 address 2001:192:10:1::254/64
ipv6 rip RIPng enable
ipv6 ospf 1 area 0
!
router ospf 1
router-id 192.10.1.254
log-adjacency-changes
redistribute connected subnets route-map LO51515151
network 192.10.1.254 0.0.0.0 area 51
!
router rip
version 2
redistribute connected metric 7 route-map LOOPBACKS
network 192.10.1.0
distribute-list prefix LOOPBACKS out
!
router bgp 254
no synchronization
bgp log-neighbor-changes
neighbor RACKS peer-group
neighbor RACKS remote-as 200
neighbor RACKS password CISCO
neighbor 2001:192:10:1::100 remote-as 200
neighbor 192.10.1.1 peer-group RACKS
neighbor 192.10.1.2 peer-group RACKS
neighbor 192.10.1.3 peer-group RACKS
neighbor 192.10.1.4 peer-group RACKS
neighbor 192.10.1.5 peer-group RACKS
neighbor 192.10.1.6 peer-group RACKS
neighbor 192.10.1.7 peer-group RACKS
neighbor 192.10.1.8 peer-group RACKS
neighbor 192.10.1.9 peer-group RACKS
neighbor 192.10.1.10 peer-group RACKS
no auto-summary
!
address-family ipv4 multicast
no auto-summary
no synchronization
exit-address-family
!
address-family ipv6
neighbor 2001:192:10:1::100 activate
network 2001:205:90:31::/64
network 2001:220:20:3::/64
network 2001:222:22:2::/64
exit-address-family
!
address-family ipv4
redistribute connected route-map LOOPBACKS
neighbor RACKS activate
neighbor RACKS route-map BGP_IN in
neighbor RACKS route-map BGP_OUT out
no neighbor 2001:192:10:1::100 activate
neighbor 192.10.1.1 peer-group RACKS
neighbor 192.10.1.2 peer-group RACKS
neighbor 192.10.1.3 peer-group RACKS
neighbor 192.10.1.4 peer-group RACKS
neighbor 192.10.1.5 peer-group RACKS
neighbor 192.10.1.6 peer-group RACKS
neighbor 192.10.1.7 peer-group RACKS
neighbor 192.10.1.8 peer-group RACKS
neighbor 192.10.1.9 peer-group RACKS
neighbor 192.10.1.10 peer-group RACKS
no auto-summary
no synchronization
exit-address-family
!
ip http server
ip classless
!
ip as-path access-list 1 permit ^$
!
!
ip prefix-list DEFAULT seq 5 permit 0.0.0.0/0
!
ip prefix-list LOOPBACKS seq 5 permit 205.90.31.0/24
ip prefix-list LOOPBACKS seq 10 permit 220.20.3.0/24
ip prefix-list LOOPBACKS seq 15 permit 222.22.2.0/24
!
logging trap debugging
logging 192.10.1.42
ipv6 router ospf 1
router-id 192.10.1.254
log-adjacency-changes
redistribute connected route-map OSPFv3_LOOPBACK
!
ipv6 router rip RIPng
distribute-list prefix-list RIPng out
!
!
!
ipv6 prefix-list OSPFv3_LOOPBACK seq 5 permit 2001:51:51:51::/64
!
ipv6 prefix-list RIPng seq 5 permit 2001:205:90:31::/64
ipv6 prefix-list RIPng seq 10 permit 2001:220:20:3::/64
ipv6 prefix-list RIPng seq 15 permit 2001:222:22:2::/64
route-map LO51515151 permit 10
match interface Loopback51515151
!
route-map OSPFv3_LOOPBACK permit 10
match ipv6 address prefix-list OSPFv3_LOOPBACK
!
route-map BGP_IN deny 10
match ip address prefix-list DEFAULT
!
route-map BGP_IN permit 10000
!
route-map LOOPBACKS permit 10
match ip address prefix-list LOOPBACKS
!
route-map BGP_OUT permit 10000
match as-path 1
!
alias exec c conf t
alias exec s show run
alias exec r show ip route
privilege exec level 0 telnet
privilege exec level 0 traceroute
privilege exec level 0 ping
privilege exec level 1 terminal length
privilege exec level 1 terminal
privilege exec level 0 show ip bgp neighbors
privilege exec level 0 show ip bgp summary
privilege exec level 0 show ip bgp
privilege exec level 0 show ip route
privilege exec level 0 show ip protocols
privilege exec level 0 show ip
privilege exec level 0 show
!
line con 0
exec-timeout 0 0
line aux 0
no exec
transport input all
line vty 0 4
exec-timeout 0 15
privilege level 0
no login
!
ntp authentication-key 1 md5 CISCO
ntp master 4
end
On 8/11/07, mohammed shoeb ahmed <mdshoeb@gmail.com> wrote:
>
> My wild guess, you might be running some other routing protocol with BB
> which has lower AD, it happened to me as well.
>
> Rip might be working fine but when give a command "sh ip route rip" you
> will see nothing. but if you see other protocol like OSPF, Eigrp or any one
> which has lower AD rip it will take all the routes.
>
> HTH
>
>
> --
> Best Regards,
>
> Mohammed Shoeb Ahmed
>
> Sr. Consultant,
> CCIE 18379
-- MCSE-MCSA 2K & 2K3: Security-Messaging MCDST, MCDBA, MCT, CEH, CISSP CCNA, CCSP, CNA 6, CCA, HP MASE Server+, I-Net+, Security+, Network+, A+
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:10 ART