You are here

Trying to track dow and fix DtD connections failing

13 posts / 0 new
Last post
wa2ise
wa2ise's picture
Trying to track dow and fix DtD connections failing

In the thread "VLAN Setup for Ubiquiti AirRouterHP ?" I've been having trouble with a DtD link between my Bullet M2, a AirRouter HP and a NanoStation m900.
This connection usually fails between the Bullet and the other two devices every day or two.   My house router network is connected to the Airrouter WAN port, and I have a GS105E serving the Nanostation (splitting the WAN, LAN and DtD to individual ports) and a GS108Ev3 serving the Bullet (splitting the WAN, LAN and DtD to individual ports).  the house router is connected to the WANs. The DtD ports are all connected together (I'm currently using two ports on the GS105 for DtD ports only, and one of these ports goes to the GS108Ev3 DtD port (the Bullet's) and the other goes to the Airrouter port 4 (which is configured as its Dtd port).  I suppose the pair of DtD ports belong to the Nanostation. 

Some background (I'm quoting various posts from the other thread so people not familiar can make some sense of this ?

My post of July 19th: "I've had problems with such a switch on just the DtD cables losing the DtD connections.  So far, using two ports on my air router (as described in my post above) as DtDs works better. 
Opened up the switch, a Netgear FS608v3, and sure enough it uses a Realtek chip RTL82095B.   Seems Realtek chips have problems maintaining an ethernet connection to the on-board switch when ports are being used in both a tagged and untagged mode.  Source: http://www.broadband-hamnet.org/documentation/202-dtd-linking-on-linksys.html   Is everything on the DtD link tagged?"

My post of July 20th:  "Without the switch, I still had connections on my DtD links drop.  So maybe the switch isn't the problem...  Presently my system consists of a Bullet M2, a Netgear GS108Ev3, an AirRouter HP M2 (with a 2nd DtD link added), and a NanoStation Loco M900 with a Netgear GS105E.  All their DtD ports are connected together (via the pair of DtD ports on the AirRouter), and all the WANs are connected to my home network's router.  I also have an IP camera DLink DCS-1100 connected to the Air Router's LAN.  I also have a pair of Linksys WRT54Gs in the house, but those are connected only by RF links, but they are also connected to the house router via their LANs (DHCP disabled).  They also have a DtD link between them, but not to the Ubiquiti's.  Everything has a few services on them, small web pages. 

Rebooting the Bullet didn't clear the problem, but the problem did clear after I then rebooted the NanoStation.  I don't know if only rebooting the NanoStation would have done it.  In the past, power cycling the GS108Ev2 would fix it (when I was using the switch with the Realtek chip in it). 

As a new test, I created a 2nd vlan2 port on my GS105E (the one that feeds the NanoStation) to connect the Bullet M2 to.  The other vlan2 port now goes to the DtD port 4 of the AirRouter.  Maybe the Airrouter doesn't like having two DtDs on it? "

AE6XE replys: When you added the 2nd DtDlink port on the airRouter, you might need to remove it from being part of the LAN at the same time.   We keep finding problems that the internal switches do not work when doing tagged and untagged on the same port.   ...hence why the NS M5 XW has DtDlink/WAN only on the secondary port."

I did this so this shouldn't be a problem.

My post July 21: ""As a new test, I created a 2nd vlan2 port on my GS105E (the one that feeds the NanoStation) to connect the Bullet M2 to.  The other vlan2 port now goes to the DtD port 4 of the AirRouter.  Maybe the Airrouter doesn't like having two DtDs on it? "

That wasn't it.  Tried rebooting the Airrouter, nope, The Nanostation, nope, the Bullet, nope. I rebooted the GS105E and that got the connections reestablished.  Maybe rebooting this tickled the GS108Ev3 into reestablishing the DtD link?.  Okay maybe the GS108Ev3 isn't good for serving both the Bullet's DtD, LAN and WANs along with unrelated computers also connected to WAN ports.

I'm trying to systemically narrow down to the root cause.  By trial and error, takes a while.  I've done validation at various jobs I've had, and trying to change one variable at a time..."

KG6JEI  replys: "Were starting to get off topic of this thread, a new thread would be better so everyone subscribed to this one doesn't get updates that are not related to the original post.

That said sounds like you have configuration issues going on in your environment. I've used isolated networks with mesh nodes on the same switch (v2 however) and not had any issues at all."

So this is the new thread. 

I since edited my July 21 post to add: I used the Netgear switch to split off these WANs (placed between the house router and the GS108Ev3) so the GS108Ev3 doesn't have to feed computers tied to the WAN.  The Netgear switch is now handling them, and the GS108Ev2 does not now see them.  The GS108Ev3 now only handles the Bullet's WAN,LAN and the DtD." 

Before I saw KG6JEI's reply. 

As for configuration issues, I wouldn't be surprised if I do have errors there, I'm mainly a hardware guy, and not much of a SW guy.  So  I'm trying to segment the system with isolated hardware... 

I do have a pair of Linksys WRT54Gs in the house, but they are NOT connected to the DtD link.  Only over the air, and they are connected to the house router, don't know if that could cause trouble...

KG6JEI
Since you note in the other
Since you note in the other thread you have modified the configs make sure all devices are STOCK and have no config files modified manually before continuing any further.

If you need to reset a device it can be done by holding the reset button for 15 seconds, the node will restart and be in preconfig mode and you can re-enter the details.

If any device has modified configs the device will not be considered for support.

After that as noted support data files will be required from the time the issue is occurring for anyone here to evaluate the situation.
AE6XE
AE6XE's picture
WA2ISE,  screen shots of the
WA2ISE,  screen shots of the GS105E and GS108E configs will help to validate the settings. ...with summary of what devices are plugged in to a given port and cat5 between switches. 
wa2ise
wa2ise's picture
Here are screengrabs of both
Here are screengrabs of both GS105 and 108. 
Image Attachments: 
wa2ise
wa2ise's picture
And more screengrabs. 

And more screengrabs.  Currently there are no switches on the DtD links.  Currently the GS's do not serve anything other than the Ubiquiti nodes.  I did have a laptop connected to an extra WAN on the GS108Ev3, but I moved that off there to an external switch connected directly to the house router.  On the AirRouter I have a DLink camera on one of the AirRouter LAN ports.  

Image Attachments: 
AE6XE
AE6XE's picture
WA2ISE,  nothing jumped out
WA2ISE,  nothing jumped out as being in conflict.  

A couple suggestions:

There is one efficiency improvement that can be made.    you can have both vlan 1 and vlan 2 defined on port 4 on both switches, then free up port 5 on the GS105E for another purpose.   You have a 'trunk' cable going between the switches, so you can add as many tags going across it as you want and then split out to the respective ports on each side.  Thus, the NS on port 1 of the GS105E can reach your home network across this trunked cable on the other switch--don't need 2 cables to your home network.

To fully bullet proof the setup, also add this additional config setting.  Create a vlan 11 on the GS105E.   Add port 3 as only port on vlan 11.   set PVID port 3 to vlan 11.   If the airRouter for some unknown reason spits out an untagged packet on this "DtDLink" port, you don't wan't to consider it DtDlink traffic on the switch--we make it a dead end on the switch (or put it to the freed up port 5 as a LAN port, maybe you have a different mesh node plugged into it some day).   Do similar on port 4 for both switches--do not redefine untagged traffic as dtdlink--would be in error if such traffic existed.  (Maybe this is contributing to the symptoms.)

Joe AE6XE
wa2ise
wa2ise's picture
Joe, I just did the untagged
Joe, I just did the untagged dead ends as you suggested.  As I have a pair of DtD ports (3 and 4) on the GS105E, I have a PVID of 11 untagged on port 3 and another PVID of 12 untagged on port 4.  And on the GS108Ev3 port 4 I created a PVID of 11 untagged. 

I'll wait a few days before trying the efficiency improvements, as I want to change only one class of thing at a time. 

73s  Bob
KX5DX
Have you verified that you have a good cable between the switch

"That wasn't it.  Tried rebooting the Airrouter, nope, The Nanostation, nope, the Bullet, nope. I rebooted the GS105E and that got the connections reestablished.  Maybe rebooting this tickled the GS108Ev3 into reestablishing the DtD link?.  Okay maybe the GS108Ev3 isn't good for serving both the Bullet's DtD, LAN and WANs along with unrelated computers also connected to WAN ports."

Have you verified that you have a good cable between the switches? The ports might be getting errors or collisions until the switch eventually disables the port. We call that "errordisable" state in Cisco world. Not sure how those Netgear switches behave under the same conditions. 

Can you do an extended ping test through the DtD link? I mean like at least 10,000 pings of 1500 bytes, if possible. If you get less than 100% success then try replacing the cable and/or moving to different ports, and repeat the test.
 

wa2ise
wa2ise's picture
I did find that my DtD "trunk

I did find that my DtD "trunk" cable did have a problem.  I disconnected it from the DtD ports on both ends and connected one end to a WAN port (goes to the house router and internet) and the other end off the other DtD port and connected to my computer.  Even though the green and yellow lights of the computer's ethernet jack lit up, the computer couldn't see the house router.  Ran the ping test on the computer to see if it could see the house router (at 192.168.1.1) and it was pretty bad.  Found a bad connection, and the computer then could see the house router and redid the ping test.  Which now missed only one out of 9500 pings. 

I now put the cable back on the DtD ports, and now I'll see how well it holds up.

I had thought that if a cable makes the green and yellow ethernet jack lights light up, it was good.  ...   Lesson learned. 

Right now, for additional testing, I'm looking at a web IP camera on my PC, the signal bits passing thru this DtD link cable.  No trouble after a few hours.
Did some more ping testing, no errors after about 4000 pings. 

KX5DX
Ethernet ports can come up

Ethernet ports can come up but they could have one port on full duplex and the other side on half duplex. Or like in your case, with massive amounts of errors until one of the sides gives up and stops passing traffic. On more advanced switches, you can pull up the port status and see if any errors are occurring. 

You probably had one or two pins that were barely making contact in the cable. I do remote network installs for a living and this is very common.  We have had "brand new patch cords" with wrong pin-out or even completely open. Can't trust something made as fast as possible with the lowest cost materials....

wa2ise
wa2ise's picture
It's held up the last couple

It's held up the last couple days, so that must have been it.  Thanks to all.

73s  Bob

Still up.  :-)    Looks like that definitely was what it was.  July 31th. 20:46 zulu

kg9dw
kg9dw's picture
yeah! Good job
yeah! Good job troubleshooting, and the next soul that has dtd problems hopefully will find this thread. Thanks for sharing. 

MB
wa2ise
wa2ise's picture
It's about 8 weeks later, and
It's about 8 weeks later, and no more trouble with this.    This calls for a dancing banana: 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer