New User, just bringing a T3-BB-32i online. SW: 50.1
Initially plugged into my main switch and powered up the T3-BB. The unit initially booted with its 192.168.0.3 IP address.
I was able to see this in my DHCP table in the router and reserved the MAC to a 0.150 address.
Rebooted router and the T3-BB LCD pulled the 0.150 IP.
I was never able to ping via cmd or find via search over my existing network, even though a connection obviously existed.
I grabbed a spare laptop and loaded the T3000 software and connected directly to the T3-BB with a standard patch cable (non crossover) via a USB-Ethernet dongle.
Setup the laptop on same range and a near IP (0.149). I was able to scan the T3-BB into the software.
The connection was very erratic, health was often 0% always less than 100%. Frequently dropping completely offline, freezing T3000, and every command/button/tab within T3000 was slow. When health would go to 0% cmd would no longer ping.
A restart of the T3-BB would restart the comms and things would be partially alive for a few minutes.
IF, I restart the T3-BB and immediately ping 0.150 -t for a continuous ping… All things are magic, communication/health is 100%, pings are all fast and consistent and T3000 software runs immensely better.
Ideas on why this is the case? Is the ethernet connection on the T3-BB going idle?