I cant see a problem here, but I have been caught on this one before when using MD5 authentication. Remember when using MD5 authentication in Area 0 the R2 will have a direct connection into Area 0 after the virtual link has been made so needs to have MD5 authentication as well. You can also do MD5 authentication on the virtual link itself, this was what I was trying to do and got confused with the MD5 authentication between R2 and Area 0. When I removed all the MD5 authentication it still would come up. In the end I removed the config and started again, bingo it came up
----- Original Message ----- From: "Kevin Love" To: Sent: Wednesday, May 28, 2003 5:37 AM Subject: Virtual Link Problem [7:69640] > Hey Team, > > I cannot figure this out. I've configured lots of virtual links, but no > matter what I do this isn't working. I had md5 authentication configured > for Area 0, but to isolate the problem, I removed authentication and the > virtual link still isn't up. I need another set of eyes (or two) looking at > this. Please help if you can! > > Here's the topology: > > Area 2 (Loopback 0) > | > R2 > \ > \ > FR > Area 1 > / \ > R5 R6 > \ / > Area 0 > Ethernet > > Here are the salient config snippets: > > R2 > ! > interface Loopback0 > ip address 192.168.2.2 255.255.255.255 > ip ospf network point-to-point > ! > interface Serial1.256 multipoint > ip address 172.16.56.2 255.255.255.248 > ip ospf priority 255 > frame-relay map ip 172.16.56.2 105 > frame-relay map ip 172.16.56.5 105 broadcast > frame-relay map ip 172.16.56.6 106 broadcast > no frame-relay inverse-arp > ! > router ospf 1 > log-adjacency-changes > area 1 virtual-link 192.168.5.5 > area 1 virtual-link 192.168.6.6 > network 172.16.56.0 0.0.0.7 area 1 > network 192.168.2.2 0.0.0.0 area 2 > ! > > R5 > > interface Ethernet0 > ip address 172.16.200.5 255.255.255.128 > ip ospf hello-interval 15 > ! > interface Serial0 > ip address 172.16.56.5 255.255.255.248 > encapsulation frame-relay > ip ospf network point-to-multipoint > frame-relay map ip 172.16.56.2 501 broadcast > frame-relay map ip 172.16.56.5 501 > frame-relay map ip 172.16.56.6 501 broadcast > no frame-relay inverse-arp > frame-relay lmi-type cisco > ! > router ospf 1 > log-adjacency-changes > area 1 virtual-link 192.168.2.2 > network 172.16.56.0 0.0.0.7 area 1 > network 172.16.200.0 0.0.0.127 area 0 > network 192.168.5.5 0.0.0.0 area 5 > ! > > R6 > > interface Serial0 > ip address 172.16.56.6 255.255.255.248 > encapsulation frame-relay > ip ospf network point-to-multipoint > frame-relay map ip 172.16.56.2 601 broadcast > frame-relay map ip 172.16.56.5 601 broadcast > frame-relay map ip 172.16.56.6 601 > no frame-relay inverse-arp > frame-relay lmi-type cisco > ! > interface FastEthernet0 > ip address 172.16.200.6 255.255.255.128 > ip ospf hello-interval 15 > half-duplex > ! > router ospf 1 > log-adjacency-changes > area 1 virtual-link 192.168.2.2 > network 172.16.56.0 0.0.0.7 area 1 > network 172.16.200.0 0.0.0.127 area 0 > network 192.168.6.6 0.0.0.0 area 6 > ! > > R2#sh ip ospf vir > Virtual Link OSPF_VL5 to router 192.168.5.5 is down > Run as demand circuit > DoNotAge LSA allowed. > Transit area 1, Cost of using 65535 > Transmit Delay is 1 sec, State DOWN, > Timer intervals configured, Hello 10, 40, Wait 40, Retransmit 5 > Virtual Link OSPF_VL4 to router 192.168.6.6 is down > Run as demand circuit > DoNotAge LSA allowed. > Transit area 1, Cost of using 65535 > Transmit Delay is 1 sec, State DOWN, > Timer intervals configured, Hello 10, 40, Wait 40, Retransmit 5 > R2# > > Trust me on the router-IDs for the virtual link statements - I have > triple-checked them. I have reloaded the routers with no luck. What am I > missing here?! > > Thanks! > Kevin Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=69653&t=69640 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
