Try building virtual-link between R5 and SW2. -- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert
YES! We include 400 hours of REAL rack time with our Blended Learning Solution! Mailto: [email protected] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Web: http://www.ipexpert.com/ On Sat, May 29, 2010 at 17:04, amit chopra <[email protected]> wrote: > Hi Guys > > In below topology , The network 88.88.88.0 which redistributed on SW2 in > NSSA is not translating by R5 NSSA (border router). Can you please let me > know why is it not advertise to R3 > > > > R3 s1/0-------- Frame Relay -----------s1/0 R5 E0/0---------------- NSSA > ---------------SW2 (loopback 88.88.88.88 redistribute into OSPF : NSSA) > > 155.1.0.0/24 (Area0) > 155.1.58.0/24 (Area 58) > > > > R3 : 155.1.0.3 (S1/0) > > R5 : 155.1.0.5 (S1/0) and 155.1.58.5 (E0/0) > > SW2 : 155.1.58.8 (VLAN 58) > > > > router-id for R5 is 150.1.5.5 , R3 : 150.1.3.3 , SW2 : 150.1.8.8 > > > > > > > > Rack1SW2#sh run | sec router ospf > > router ospf 1 > > router-id 150.1.8.8 > > log-adjacency-changes > > area 58 nssa > > redistribute connected subnets route-map RED > > network 150.1.8.8 0.0.0.0 area 58 > > network 155.1.58.8 0.0.0.0 area 58 > > network 155.1.108.8 0.0.0.0 area 108 > > > > The route-map RED is matching access-list 88 for network 88.88.88.0 > > > > On R5 > > > > Rack1R5#show ip route 88.88.88.0 > > Routing entry for 88.88.88.0/24 > > Known via "ospf 1", distance 110, metric 20, type NSSA extern 2, forward > metric 11 > > Last update from 155.1.58.8 on Ethernet0/0, 00:07:55 ago > > Routing Descriptor Blocks: > > * 155.1.58.8, from 150.1.8.8, 00:07:55 ago, via Ethernet0/0 > > Route metric is 20, traffic share count is 1 > > > > > > Rack1R5#sh run | sec router ospf > > router ospf 1 > > router-id 150.1.5.5 > > log-adjacency-changes > > area 58 nssa > > network 150.1.5.5 0.0.0.0 area 0 > > network 155.1.0.5 0.0.0.0 area 0 > > network 155.1.5.5 0.0.0.0 area 0 > > network 155.1.45.5 0.0.0.0 area 45 > > network 155.1.58.5 0.0.0.0 area 58 > > neighbor 155.1.0.3 > > > > > > Rack1R5#show ip ospf database external 88.88.88.0 > > > > OSPF Router with ID (150.1.5.5) (Process ID 1) > > > > > > Rack1R5#show ip ospf database nssa-external 88.88.88.0 > > > > OSPF Router with ID (150.1.5.5) (Process ID 1) > > > > Type-7 AS External Link States (Area 58) > > > > Routing Bit Set on this LSA > > LS age: 1271 > > Options: (No TOS-capability, No Type 7/5 translation, DC) > > LS Type: AS External Link > > Link State ID: 88.88.88.0 (External Network Number ) > > Advertising Router: 150.1.8.8 > > LS Seq Number: 80000003 > > Checksum: 0xFC47 > > Length: 36 > > Network Mask: /24 > > Metric Type: 2 (Larger than any link state path) > > TOS: 0 > > Metric: 20 > > Forward Address: 150.1.8.8 > > External Route Tag: 0 > > > > On R3 : > > > > Rack1R3#show ip route 88.88.88.0 > > % Network not in table > > Rack1R3# > > Rack1R3#ping 150.1.8.8 > > > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 150.1.8.8, timeout is 2 seconds: > > !!!!! > > Success rate is 100 percent (5/5), round-trip min/avg/max = 8/12/20 ms > > Rack1R3#ping 155.1.58.8 > > > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 155.1.58.8, timeout is 2 seconds: > > !!!!! > > Success rate is 100 percent (5/5), round-trip min/avg/max = 12/20/44 ms > > Rack1R3#ping 155.1.58.5 > > > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 155.1.58.5, timeout is 2 seconds: > > !!!!! > > Success rate is 100 percent (5/5), round-trip min/avg/max = 4/8/12 ms > > Rack1R3# > > > > I am able to reach router-id of SW2 but not able to ping 88.88.88.0 > > > > can anyone know why is it happening > > > > Regards > Amit > > > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
