Thanks, missed that :(

-----Original Message-----
From: Marko Milivojevic [mailto:[email protected]] 
Sent: September-26-10 8:14 AM
To: Jason Maynard
Cc: Áki Hermann Barkarson; CCIE OSL
Subject: Re: [OSL | CCIE_RS] sham-link bug?

He has that covered with "redistribute connected".

--
Marko Milivojevic - CCIE #18427
Senior Technical Instructor - IPexpert

FREE CCIE training: http://bit.ly/vLecture

Mailto: [email protected]
Telephone: +1.810.326.1444
Web: http://www.ipexpert.com/

On Sun, Sep 26, 2010 at 11:57, Jason Maynard <[email protected]> wrote:
> I might be missing something but I do not see the loopback interfaces for
> the shamlink being advertised into BGP
>
>
>
> Note: You should not advertise the interfaces directly into OSPF.
>
>
>
>
>
>
>
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Áki Hermann
> Barkarson
> Sent: September-25-10 2:26 PM
> To: CCIE OSL
> Subject: [OSL | CCIE_RS] sham-link bug?
>
>
>
> Hey guys,
>
>
>
> I got a little problem with a sham-link lab i was doing. It‘s my own
> scenario.. it‘s R2+R4 connected with rip+ldp+mpbgp.. on each side there is a
> client facing interface connected with ospf.. router2 has client area2 and
> router4 has client area4 and then i setup a sham-link area0 between them..
> then i redistribute ospf into bgp .. but i skip redistributing bgp back into
> ospf, don‘t care about that step for this test.
>
>
>
> ## I entered my config and everything comes up fine except the sham-links...
> here are some commands
>
>
>
> R2#sh ip route rip
>
> R       4.4.4.4 [120/1] via 10.2.3.3, 00:00:20, FastEthernet0/1
>
> R4#sh ip route rip
>
> R       2.2.2.2 [120/1] via 10.2.3.2, 00:00:10, FastEthernet0/0
>
> R2#sh mpls ldp neigh
>
>     Peer LDP Ident: 4.4.4.4:0; Local LDP Ident 2.2.2.2:0
>
> <<>>
>
> R4#sh mpls ldp neigh
>
>     Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 4.4.4.4:0
>
> <<>>
>
> R2#sh ip bgp vpnv4 all summ | b ^N
>
> Neighbor        V          AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down
> State/PfxRcd
>
> 4.4.4.4         4         24      38      47        9    0    0
> 00:04:22        2
>
> R4#sh ip bgp vpnv4 all summ | b ^N
>
> Neighbor        V          AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down
> State/PfxRcd
>
> 2.2.2.2         4         24      42      44        9    0    0
> 00:04:15        2
>
> R2#sh ip route vrf client 100.100.100.4
>
> Routing entry for 100.100.100.4/32
>
> <<>>
>
> R4#sh ip route vrf client 100.100.100.2
>
> Routing entry for 100.100.100.2/32
>
> <<>>
>
>
>
> ## Looks fine.. so i check ping
>
>
>
> R2#ping vrf client 100.100.100.4 so lo1
>
> <<>>
>
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
>
>
>
> R4#ping vrf client 100.100.100.2 so lo1
>
> <<>>
>
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
>
>
>
> ## Yet the sham-links refuse to come up..
>
>
>
> R2#sh ip ospf sham
>
> Sham Link OSPF_SL1 to address 100.100.100.4 is down
>
> <<>>
>
> R4#sh ip ospf sham
>
> Sham Link OSPF_SL2 to address 100.100.100.2 is down
>
> <<>>
>
>
>
> ## I tried some various debugging and didn‘t find anything there that seemed
> relevant.. but when i tried removing only the sham-link lines from ospf
> proccess and re-entering them.. voila.. the links came up..
>
>
>
> R2(config-router)# no area 0 sham-link 100.100.100.2 100.100.100.4
>
> R2(config-router)# area 0 sham-link 100.100.100.2 100.100.100.4
>
> R4(config-router)# no  area 0 sham-link 100.100.100.4 100.100.100.2
>
> R4(config-router)# area 0 sham-link 100.100.100.4 100.100.100.2
>
>
>
> *Sep 25 19:21:18.174: %OSPF-5-ADJCHG: Process 1, Nbr 2.2.2.2 on OSPF_SL4
> from LOADING to FULL, Loading Done
>
>
>
> ## When i reboot the sham-links don‘t come up either unless i remove the
> sham-link lines and re-enter them..
>
> ## I did a quick google and it seems to be happening to people.. I‘m
> wondering whether this is due to misconfig or bug..
>
> ## Seems bugged to me.. here are my configs:
>
>
>
>
>
> ####
>
> #R2# (actually using R1 in the proctor labs rack even though i call it R2)
>
> ####
>
>
>
> Current configuration : 2169 bytes
>
> !
>
> version 12.4
>
> service timestamps debug datetime msec
>
> service timestamps log datetime msec
>
> no service password-encryption
>
> !
>
> hostname R2
>
> !
>
> boot-start-marker
>
> boot-end-marker
>
> !
>
> logging message-counter syslog
>
> !
>
> no aaa new-model
>
> memory-size iomem 15
>
> !
>
> dot11 syslog
>
> ip source-route
>
> !
>
> ip cef
>
> !
>
> ip vrf client
>
>  rd 1:1
>
>  route-target export 2:4
>
>  route-target import 2:4
>
> !
>
> no ip domain lookup
>
> no ipv6 cef
>
> !
>
> multilink bundle-name authenticated
>
> !
>
> mpls label protocol ldp
>
> !
>
> voice-card 0
>
> !
>
> archive
>
>  log config
>
>   hidekeys
>
> !
>
> interface Loopback0
>
>  ip address 2.2.2.2 255.255.255.255
>
> !
>
> interface Loopback1
>
>  ip vrf forwarding client
>
>  ip address 100.100.100.2 255.255.255.255
>
> !
>
> interface FastEthernet0/0
>
>  ip vrf forwarding client
>
>  ip address 10.1.2.2 255.255.255.0
>
>  duplex auto
>
>  speed auto
>
> !
>
> interface FastEthernet0/1
>
>  ip address 10.2.3.2 255.255.255.0
>
>  duplex auto
>
>  speed auto
>
>  mpls ip
>
> !
>
> router rip
>
>  version 2
>
>  passive-interface default
>
>  no passive-interface FastEthernet0/1
>
>  network 0.0.0.0
>
>  no auto-summary
>
> !
>
> router ospf 1 vrf client
>
>  router-id 2.2.2.2
>
>  log-adjacency-changes
>
>  area 0 sham-link 100.100.100.2 100.100.100.4
>
>  network 10.1.2.2 0.0.0.0 area 2
>
> !
>
> router bgp 24
>
>  bgp router-id 2.2.2.2
>
>  no bgp default ipv4-unicast
>
>  bgp log-neighbor-changes
>
>  neighbor 4.4.4.4 remote-as 24
>
>  neighbor 4.4.4.4 update-source Loopback0
>
>  !
>
>  address-family vpnv4
>
>   neighbor 4.4.4.4 activate
>
>   neighbor 4.4.4.4 send-community both
>
>  exit-address-family
>
>  !
>
> address-family ipv4 vrf client
>
>   redistribute connected
>
>   redistribute ospf 1 vrf client route-map no-lo0
>
>   no synchronization
>
>  exit-address-family
>
> !
>
> ip forward-protocol nd
>
> no ip http server
>
> no ip http secure-server
>
> !
>
> route-map no-lo0 deny 10
>
>  match interface Loopback0
>
> !
>
> route-map no-lo0 permit 20
>
> !
>
> mpls ldp router-id Loopback0
>
> !
>
> control-plane
>
> !
>
> line con 0
>
>  exec-timeout 0 0
>
> line aux 0
>
> line vty 0 4
>
>  login
>
> !
>
> scheduler allocate 20000 1000
>
> end
>
>
>
> ####
>
> #R4#
>
> ####
>
>
>
> Current configuration : 2267 bytes
>
> !
>
> version 12.4
>
> service timestamps debug datetime msec
>
> service timestamps log datetime msec
>
> no service password-encryption
>
> !
>
> hostname R4
>
> !
>
> boot-start-marker
>
> boot-end-marker
>
> !
>
> logging message-counter syslog
>
> !
>
> no aaa new-model
>
> memory-size iomem 10
>
> !
>
> dot11 syslog
>
> ip source-route
>
> !
>
> !
>
> ip cef
>
> !
>
> ip vrf client
>
>  rd 1:1
>
>  route-target export 2:4
>
>  route-target import 2:4
>
> !
>
> no ip domain lookup
>
> no ipv6 cef
>
> !
>
> multilink bundle-name authenticated
>
> !
>
> mpls label protocol ldp
>
> !
>
> voice-card 0
>
> !
>
> archive
>
>  log config
>
>   hidekeys
>
> !
>
> interface Loopback0
>
>  ip address 4.4.4.4 255.255.255.255
>
> !
>
> interface Loopback1
>
>  ip vrf forwarding client
>
>  ip address 100.100.100.4 255.255.255.255
>
> !
>
> interface FastEthernet0/0
>
>  ip address 10.2.3.3 255.255.255.0
>
>  duplex auto
>
>  speed auto
>
>  mpls ip
>
> !
>
> interface FastEthernet0/1
>
>  ip vrf forwarding client
>
>  ip address 10.3.4.4 255.255.255.0
>
>  duplex auto
>
>  speed auto
>
> !
>
> interface Serial0/0/0
>
>  no ip address
>
>  shutdown
>
> !
>
> interface Serial0/1/0
>
>  no ip address
>
>  shutdown
>
> !
>
> router rip
>
>  version 2
>
>  passive-interface default
>
>  no passive-interface FastEthernet0/0
>
>  network 0.0.0.0
>
>  no auto-summary
>
> !
>
> router ospf 1 vrf client
>
>  router-id 4.4.4.4
>
>  log-adjacency-changes
>
>  area 0 sham-link 100.100.100.4 100.100.100.2
>
>  network 10.3.4.4 0.0.0.0 area 4
>
> !
>
> router bgp 24
>
>  bgp router-id 4.4.4.4
>
>  no bgp default ipv4-unicast
>
>  bgp log-neighbor-changes
>
>  neighbor 2.2.2.2 remote-as 24
>
>  neighbor 2.2.2.2 update-source Loopback0
>
>  !
>
>  address-family vpnv4
>
>   neighbor 2.2.2.2 activate
>
>   neighbor 2.2.2.2 send-community both
>
>  exit-address-family
>
>  !
>
> address-family ipv4 vrf client
>
>   redistribute connected
>
>   redistribute ospf 1 vrf client route-map no-lo0
>
>   no synchronization
>
>  exit-address-family
>
> !
>
> ip forward-protocol nd
>
> no ip http server
>
> no ip http secure-server
>
> !
>
> route-map no-lo0 deny 10
>
>  match interface Loopback0
>
> !
>
> route-map no-lo0 permit 20
>
> !
>
> mpls ldp router-id Loopback0
>
> !
>
> control-plane
>
> !
>
> line con 0
>
>  exec-timeout 0 0
>
> line aux 0
>
> line vty 0 4
>
>  login
>
> !
>
> scheduler allocate 20000 1000
>
> end
>
>
>
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>

_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to