Re: [WISPA] Mikrotik OSPF Problem
I have seen this with switches, as well as PoE injectors! Don't tell me how a POE injector could cause OSPF to not function correctly, but as soon as it was replaced, it came up. --- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer Link Technologies, Inc -- Mikrotik WISP Support Services Office: 314-735-0270 Website: http://www.linktechs.net http://www.linktechs.net/ LIVE On-Line Mikrotik Training http://www.onlinemikrotiktraining.com - Author of Learn RouterOS http://www.routerosbook.com/ From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Scott Reed Sent: Sunday, August 15, 2010 10:25 PM To: WISPA General List Subject: Re: [WISPA] Mikrotik OSPF Problem I will power cycle the switch tomorrow. It is an industrial DIN-rail mount that is not managed. Scott Lambert wrote: On Sun, Aug 15, 2010 at 08:11:39PM -0400, Scott Reed wrote: That all makes sense, but I think I have eliminated most of it. The link from device A to device B is the primary link for this part of the network to the Internet. It is carrying 2-way traffic just fine. That would seem to indicate that all the hardware level stuff is OK. I have looked at the interfaces, but I will do it again to be sure I have not missed one, but since this plugs into a switch it should just be the one port on the at fault unit and the switch. The other part of the mystery is that this was working fine and then just quit. As far as I know there were no changes to the network near the time it quit finding neighbors. The problem may be that the switch has failed to forward multicast traffic from this port. Normal traffic would flow correctly. Have you power cycled the switch? Is it a managed switch? Does it have the ablility to permit or deny multicast traffic on a port by port basis? -- Scott Reed Sr. Systems Engineer GAB Midwest 1-800-363-1544 x2241 1-260-827-2241 Cell: 260-273-7239 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik OSPF Problem
On Sun, 2010-08-15 at 20:11 -0400, Scott Reed wrote: That all makes sense, but I think I have eliminated most of it. While it may seem that nothing has changed, it is certain that SOMETHING has changed. Some things to try: * Run a packet capture on both ends of the link looking for protocol 89 (OSPF). You'll be looking for the hello packets. * Assuming you see these packets at both locations, you should check for firewall changes at the remote end. Then end that shows init state IS seeing the hellos, so it is the OTHER end that is NOT. * If you are seeing the hello on both ends, the next thing would be to restart OSPF on the remote end. You should be able to restart OSPF on just that one interface. With Mikrotik, you can do that by disable/enable the network under ROUTING-OSPF-Network. * If you are NOT seeing the hello packets on the remote side, then you'll need to ensure that the link between these 2 devices is able to pass multicast traffic. * If all else fails, rebooting the remote devices or the link may help. * Call me and I'll help you troubleshoot further. 573-276-2879. -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://store.wispgear.net/* Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik OSPF Problem
Butch - your post was fine except for the first sentence. No need to pick at wounds at this point. Let it go. Matt Larsen vistabeam.com On 8/15/2010 5:49 PM, Butch Evans wrote: On Sat, 2010-08-14 at 17:15 -0400, Scott Reed wrote: I have an RB433AH running ROS3.30. It has been running well for months or longer. Yesterday afternoon it lost the OSPF routes that come in from the backhaul interface. I rebooted. Still no go. It showed 9 potential neighbors in Init state on that interface. It gets neighbors on the wireless AP interface. I power cycled it this morning. Same thing, 9 neighbors in Init state. On of those neighbors is inches away so I put a 3 foot jumper between ether2 on the bad unit to ether2 on the good one. They instantly became neighbors. What do I need to look for on the interface that is not working to get it to go to the next step? By the way, that interface is the link to the Internet for 2 APs and all of the customers on those 2 APs are moving traffic, so it is not a physical interface that is not working. Hopefully Jim Patient won't think this is advertising, so I'll post it here. It is likely that you may be seeing a duplex mismatch at some point in the network. Another possibility is that you have an incomplete bridge somewhere (backhaul maybe?), such as would occur with an 802.11 based client-ap setup. Without more information, it's hard to say what could be causing this issue. State init means that we have seen the hello(s) from the neighbor, but they have not seen ours. This indicates some failure of packets in one direction, so I am guessing a duplex problem. WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik OSPF Problem
On Sat, 2010-08-14 at 17:15 -0400, Scott Reed wrote: I have an RB433AH running ROS3.30. It has been running well for months or longer. Yesterday afternoon it lost the OSPF routes that come in from the backhaul interface. I rebooted. Still no go. It showed 9 potential neighbors in Init state on that interface. It gets neighbors on the wireless AP interface. I power cycled it this morning. Same thing, 9 neighbors in Init state. On of those neighbors is inches away so I put a 3 foot jumper between ether2 on the bad unit to ether2 on the good one. They instantly became neighbors. What do I need to look for on the interface that is not working to get it to go to the next step? By the way, that interface is the link to the Internet for 2 APs and all of the customers on those 2 APs are moving traffic, so it is not a physical interface that is not working. Hopefully Jim Patient won't think this is advertising, so I'll post it here. It is likely that you may be seeing a duplex mismatch at some point in the network. Another possibility is that you have an incomplete bridge somewhere (backhaul maybe?), such as would occur with an 802.11 based client-ap setup. Without more information, it's hard to say what could be causing this issue. State init means that we have seen the hello(s) from the neighbor, but they have not seen ours. This indicates some failure of packets in one direction, so I am guessing a duplex problem. -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://store.wispgear.net/* Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik OSPF Problem
That all makes sense, but I think I have eliminated most of it. The link from device A to device B is the primary link for this part of the network to the Internet. It is carrying 2-way traffic just fine. That would seem to indicate that all the hardware level stuff is OK. I have looked at the interfaces, but I will do it again to be sure I have not missed one, but since this plugs into a switch it should just be the one port on the at fault unit and the switch. The other part of the mystery is that this was working fine and then just quit. As far as I know there were no changes to the network near the time it quit finding neighbors. Butch Evans wrote: On Sat, 2010-08-14 at 17:15 -0400, Scott Reed wrote: I have an RB433AH running ROS3.30. It has been running well for months or longer. Yesterday afternoon it lost the OSPF routes that come in from the backhaul interface. I rebooted. Still no go. It showed 9 potential neighbors in Init state on that interface. It gets neighbors on the wireless AP interface. I power cycled it this morning. Same thing, 9 neighbors in Init state. On of those neighbors is inches away so I put a 3 foot jumper between ether2 on the bad unit to ether2 on the good one. They instantly became neighbors. What do I need to look for on the interface that is not working to get it to go to the next step? By the way, that interface is the link to the Internet for 2 APs and all of the customers on those 2 APs are moving traffic, so it is not a physical interface that is not working. Hopefully Jim Patient won't think this is advertising, so I'll post it here. It is likely that you may be seeing a duplex mismatch at some point in the network. Another possibility is that you have an incomplete bridge somewhere (backhaul maybe?), such as would occur with an 802.11 based client-ap setup. Without more information, it's hard to say what could be causing this issue. State init means that we have seen the hello(s) from the neighbor, but they have not seen ours. This indicates some failure of packets in one direction, so I am guessing a duplex problem. -- Scott Reed Sr. Systems Engineer GAB Midwest 1-800-363-1544 x2241 1-260-827-2241 Cell: 260-273-7239 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik OSPF Problem
On Sun, Aug 15, 2010 at 08:11:39PM -0400, Scott Reed wrote: That all makes sense, but I think I have eliminated most of it. The link from device A to device B is the primary link for this part of the network to the Internet. It is carrying 2-way traffic just fine. That would seem to indicate that all the hardware level stuff is OK. I have looked at the interfaces, but I will do it again to be sure I have not missed one, but since this plugs into a switch it should just be the one port on the at fault unit and the switch. The other part of the mystery is that this was working fine and then just quit. As far as I know there were no changes to the network near the time it quit finding neighbors. The problem may be that the switch has failed to forward multicast traffic from this port. Normal traffic would flow correctly. Have you power cycled the switch? Is it a managed switch? Does it have the ablility to permit or deny multicast traffic on a port by port basis? -- Scott LambertKC5MLE Unix SysAdmin lamb...@lambertfam.org WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik OSPF Problem
I will power cycle the switch tomorrow. It is an industrial DIN-rail mount that is not managed. Scott Lambert wrote: On Sun, Aug 15, 2010 at 08:11:39PM -0400, Scott Reed wrote: That all makes sense, but I think I have eliminated most of it. The link from device A to device B is the primary link for this part of the network to the Internet. It is carrying 2-way traffic just fine. That would seem to indicate that all the hardware level stuff is OK. I have looked at the interfaces, but I will do it again to be sure I have not missed one, but since this plugs into a switch it should just be the one port on the at fault unit and the switch. The other part of the mystery is that this was working fine and then just quit. As far as I know there were no changes to the network near the time it quit finding neighbors. The problem may be that the switch has failed to forward multicast traffic from this port. Normal traffic would flow correctly. Have you power cycled the switch? Is it a managed switch? Does it have the ablility to permit or deny multicast traffic on a port by port basis? -- Scott Reed Sr. Systems Engineer GAB Midwest 1-800-363-1544 x2241 1-260-827-2241 Cell: 260-273-7239 WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
Re: [WISPA] Mikrotik OSPF Problem
On Sat, Aug 14, 2010 at 05:15:05PM -0400, Scott Reed wrote: I have an RB433AH running ROS3.30. It has been running well for months or longer. Yesterday afternoon it lost the OSPF routes that come in from the backhaul interface. I rebooted. Still no go. It showed 9 potential neighbors in Init state on that interface. It gets neighbors on the wireless AP interface. I power cycled it this morning. Same thing, 9 neighbors in Init state. On of those neighbors is inches away so I put a 3 foot jumper between ether2 on the bad unit to ether2 on the good one. They instantly became neighbors. What do I need to look for on the interface that is not working to get it to go to the next step? By the way, that interface is the link to the Internet for 2 APs and all of the customers on those 2 APs are moving traffic, so it is not a physical interface that is not working. http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a00800949f7.shtml#trouble_neigh_states -- Scott LambertKC5MLE Unix SysAdmin lamb...@lambertfam.org WISPA Wants You! Join today! http://signup.wispa.org/ WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
