Cant troubleshoot layer one - no interface status/details

All the bells and wistles on the balance 20x and you cant even do basic layer 1 troubleshooting. I am close to smashing this thing before returning it. What a bummer. Not being able to troubleshoot layer one is a definite deal breaker. Thought I had the right product. Good thing I evaluate things before considering a deployment. Cisco, palo alto, sophos and barracudda where you at!

The information you want may be available on the support.cgi page. Just change the URL bar - delete the index.cgi?blahblahblah (everything after the MANGA/) and put in support.cgi at the end of the URL. Expand the LAN/WAN details and you can see some performance related data per port.

Thanks. ill give it a try later on today. I unfortunately had to take a break as I had become infuriated after refusing to believe the device was missing this key functionality then learning it actually was.

the support menu was pretty unhelpful regarding link status as it does not give you a break out of each port with corresponding details for each link. I still have zero clue whats plugged into what port as all the tx/rx statistics just say “lan”. I tried plugging in a machine to each port and have link lights and still just see lan after refreshing multiple times. I feel like a buffoon for thinking I was just going to be able to spit these out all over the country.

The Balance 20x is an entry level device, and while it has a pretty impressive feature set for its pricepoint, doesn’t do everything.

In this instance, the four LAN ports on the 20x are a switch chip, not individual interfaces of the main SOC. While I would also like to see Peplink give some more visibility of those interfaces (and have a feature request for that logged), that is the reason.

Higher end units that have multiple routed interfaces show more information. For example, the 310 5G shows the status & negotiation of each individual LAN port.

Other option would be to use a Peplink SD-Switch behind it, which will show all client information including what port they are connected to in InControl.

Event Log does show the negotiated speed per link/port. So you can see if it is linked at 10/100/1000Mbps, and disconnects/failing links are also logged in the Event Log. We’ve used it in the past to track layer1 errors in cables. This function also works on B20X, so seems the Switch chip in it does report that data.