Attached device responds to LLDP but nothing else

User avatar
Brough
Member
 
Posts: 93
Joined: Tue Dec 09, 2014 3:40 pm
Location: Boston, MA, USA
Has thanked: 1 time
Been thanked: 9 times

Attached device responds to LLDP but nothing else

Thu Apr 16, 2020 3:14 pm

I'm pretty sure we have no problems with the Netonix switch in question, but I can't access an attached radio and, due to the pandemic, I can't get back into the site where switch and the radio are located until some time next week. So I'm looking for ideas.

I have a radio, properly configured I believe, which gives correct IP and MAC addresses in response to LLDP but which I can't ping or log into.

The radio is a Bridgewave Flex4G-Lite that should be carrying 3 Gbps of traffic but is only carrying 1 Gbps. The radio is PoE powered (48VH) and managed via a 1 Gbps Ethernet connection from port 2 on a WS-26-400-AC switch to port 1 on the radio. The Bridgewave data path is configured as three 1 Gbps pass through links so I can't access the Bridgewave management interface through any of the data paths (I've tried). The radio was working correctly on the bench before it was swapped for the radio in the field (yesterday).

Not only can I not remotely log into the radio, but I can't ping it from the router that is its gateway and I can't ping it from the Netonix switch Ping tool.

Here's the discovery page. Any suggestions?
.
Attachments
Capture.PNG
Discovery page

User avatar
Brough
Member
 
Posts: 93
Joined: Tue Dec 09, 2014 3:40 pm
Location: Boston, MA, USA
Has thanked: 1 time
Been thanked: 9 times

Re: Attached device responds to LLDP but nothing else

Fri Apr 17, 2020 12:26 pm

OK, problem resolved. It was a configuration error on the LAG page. This site has several 2 Gbps radios so there are multiple LAGs configured on various ports. Apparently port 2 was previously in use in a 2 port LAG. That configuration was still active (and clearly visible once I looked at the LAG page). As soon as that was reset -> everything fixed.

So multiple errors:
1) when the port was freed up, it's name was blanked but it's LAG configuration wasn't stripped out.
2) when the new link was setup, the engineer didn't look at the LAG page on the Netonix (presumably because the 3 data paths go through a different switch from this management port), but sloppy none-the-less.
3) When I got involved, I didn't go over the switch configuration with a fine-tooth comb before posting my question. :(

Return to General Discussion

Who is online

Users browsing this forum: No registered users and 4 guests