Intermittent Link test and DHCP test failing

[ceejm1]

Hello,

I seem to be having intermittent issues with Link/DHCP tests failing.

Testing on a draytek vigor router and also a netgear GS116 tests operate as expected.

However, when connected to a ubiquiti toughswitch 5 port neither test completes.  A PC plugged into the same port receives DHCP and performs as expected.

When watching the unifi web interface the port becomes 'unconnected' before the test seems to finish...

If I cascade a simple switch off the toughswitch (a netgear FS105) then this holds the port 'up' on the toughswitch but the same behaviour shows on the link LED on the netgear - ie the link light goes out before the PE test appears to have completed.  The only difference with this setup is if I select only a link test then it works correctly but if i select both a link and a dhcp test both fail.

Its as though the PE is disconnecting before the tests finish yet it seems to work fine on another switches...

Its irritating not to to be able to trust a piece of test equipment - I spent a lot of time wondering why I wasn't getting DHCP on a particular VLAN on the toughswitch until I finally connected a PC and it was actually working as it should have...

Any thoughts on the matter??

Hardware version 6
Firmware version 29
App version 2.6i

James

[ceejm1]

Bump - Any thoughts on this issue?

James

[snowmanjax]

Does your ubiquiti switch have passive POE? I've seen unreliable tests on ubiquiti switches until I turned the passive POE off. As passive POE isn't a standard exactly, a decent amount of testers have issues with it. Fluke's Microscanner has issues with it as well, so I can confirm it's not just the PE device.

Hope that helps you, as it solved my issue.


snowman

[ceejm1]

It does have that option but it is turned off on the port under test.

Thanks
James

[islanderfj]

Same issue here.

Just got my PE, Hardware version 6, Firmware version 29, App Version 2.8a (Android)
Worked at home with my Asus AC3200 router, but at the office running Cisco C6880 switches.  Changed DHCP timeout to 60 seconds.  DHCP fails.  Plugged in a PC and got an IP with no issues. 

Kinda critical - you think?

[BWheetley]

I'm also having unreliable test results with the DHCP / Ping tests.  I use static IPs on our connections so it's not related to whether or not the device receives an IP address from a DHCP server.  So in the Pockethernet app I set the static IP, netmask, gateway, and DNS.  In the Ping section I set it to ping the gateway address, google's DNS server (8.8.8., and a FQDN such as www.google.com.  Sometimes all three hosts will time out.  99% of the time the gateway IP will time out and the other two will respond.  We test on Cisco 6509 with WS-X6748-GE-TX line cards as well as Cisco 4948 switches.  Ports on the Cisco side are usually set as:

 ip address X.X.X.X N.N.N.N
 no ip redirects
 no ip unreachables
 no ip proxy-arp
 speed auto 10 100
 no cdp enable
 spanning-tree portfast edge
 
-----

App:  IOS 2.6i
H/W Ver: 6
F/W:  29

[islanderfj]

I noticed something - if I turn off the Outgoing VLAN tag test, I am able to get DHCP consistently.