Why is my Obi110 unit constantly recycling???
RonR:
You indicated that changing the OBi Ethernet port from the default 10 mb/s half-duplex to 100 mb/s full-duplex made your problem worse. I simply explained how to put it back.
There have been cases where some networks didn't like the OBi running 10 mb/s half-duplex and changing to 100 mb/s full-duplex alleviated their problems. Apparently this change did not improve things for you. I don't have any further ideas at this time.
otherwhirl:
So basically you're saying i'm just stuck with a problem to deal with on my own?
Quote from: RonR on January 20, 2012, 09:24:37 pm
You indicated that changing the OBi Ethernet port from the default 10 mb/s half-duplex to 100 mb/s full-duplex made your problem worse. I simply explained how to put it back.
There have been cases where some networks didn't like the OBi running 10 mb/s half-duplex and changing to 100 mb/s full-duplex alleviated their problems. Apparently this change did not improve things for you. I don't have any further ideas at this time.
Stewart:
Is anything logged in syslog, just prior to the reboot? Or, is any information logged about the reboot cause?
otherwhirl:
Quote from: Stewart on January 21, 2012, 01:56:59 am
Is anything logged in syslog, just prior to the reboot? Or, is any information logged about the reboot cause?
Hey Stewart thanks for responding.
Please forgive me , as I am not to keen on much of the VOIP terminology.
Where would I access the "syslog" data? " is any information logged about the reboot cause?" Again, I am uncertain about where exactly I would access this information you are referring to.
Please advise.
Thanks!
Stewart:
In the OBi, set System Management -> Device Admin -> Syslog -> Server to the local IP address of your PC. On the PC, run a syslog server or Wireshark to capture the data. If you don't have one or don't know what that means, Google it. There are several free syslog daemons for Windows.
Navigation
[0] Message Index
[#] Next page
[*] Previous page