From: Joseph Brunner (joe@affirmedsystems.com)
Date: Wed Aug 22 2007 - 19:54:18 ART
If the task doesn't say don't do it, I always run "ip ospf mtu-ignore"
around the switches!
LOL they often have a 1514 svi mtu, or 1504 system mtu when running
l2tp-tunneling. 99% I run this as a best practice. If ever a task doesn't
allow it, then just adjust the ip mtu on the svi, etc. of the switch.
-Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ISolveSystems
Sent: Wednesday, August 22, 2007 6:39 PM
To: Cisco certification
Subject: IP OSPF neigh stuck in 2WAY
Hello expert,
R5(FA0/1) and R4(Fa0/0) are in VL45 as well as SW3 and SW4. For some
reason, R4 and R5 stuck in two way. All the others neighbor up. I have
turned on debugging and check the config and found nothing wrong.
Any idea?
Rack1R5(config-if)#do sh ip osp nei
Neighbor ID Pri State Dead Time Address Interface
150.1.4.4 0 FULL/ - - 129.1.54.4
Serial0/0/0.54
150.1.4.4 1 2WAY/DROTHER 00:00:39 129.1.45.4
FastEthernet0/1
150.1.9.9 1 FULL/DR 00:00:32 129.1.45.1
FastEthernet0/1
150.1.10.10 1 FULL/BDR 00:00:38 129.1.45.2
FastEthernet0/1
150.1.8.8 1 FULL/DR 00:00:34 129.1.58.8
FastEthernet0/0
Rack1R5(config-if)#
Rack1R4#sh ip osp nei
Neighbor ID Pri State Dead Time Address Interface
150.1.5.5 0 FULL/ - - 129.1.54.5
Serial0/0/0.54
150.1.6.6 1 FULL/BDR 00:00:34 129.1.46.6
FastEthernet0/1
150.1.5.5 1 2WAY/DROTHER 00:00:31 129.1.45.5
FastEthernet0/0
150.1.9.9 1 FULL/DR 00:00:37 129.1.45.1
FastEthernet0/0
150.1.10.10 1 FULL/BDR 00:00:33 129.1.45.2
FastEthernet0/0
Rack1R4#
Rack1SW3(config-if)#do sh ip osp nei
Neighbor ID Pri State Dead Time Address Interface
150.1.4.4 1 FULL/DROTHER 00:00:35 129.1.45.4 Vlan45
150.1.5.5 1 FULL/DROTHER 00:00:32 129.1.45.5 Vlan45
150.1.10.10 1 FULL/BDR 00:00:34 129.1.45.2 Vlan45
150.1.10.10 0 FULL/ - 00:00:34 129.1.34.10
Port-channel34
Rack1SW3(config-if)#
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:12 ART