Just a final update... after fighting this thing for almost a month, come to find out it was a bad Netgear gigabit switch.... now I know why I insist on cisco.
Have fun,
DAVE
toggle quoted message
Show quoted text
--- In Crestron@..., "innoventgroup" <innoventgroup@...> wrote:
Here is another piece of the pie, after thinking about your Rx error thing, I had an idea. I went into the Simpl program and commented out everything associated with the ADMS and then disconnected it from the network. WOW... all poop broke loose... now it is vertually impossible to pull up the error log and when I try I get the following error...
The socket connection was closed with socket error 10053.
hows that for fun....
Thanks,
DAVE
--- In Crestron@..., "innoventgroup" <innoventgroup@> wrote:
Ok.. it had 3 Rx overruns... one more piece of info... this seemed that it started when Crestron released their latest firmware for the ADMS.. And, now that you bring it up... that may correspond to the overruns... what do you think?
--- In Crestron@..., "Sean" <sound.scan@> wrote:
I've seen this happen with 2-series control systems when they're slammed with broadcast traffic. The HW watchdog will reset the NIC after too many RX buffer overflows. Have you added anything to your network recently? Or any software that performs automatic device discovery?
In text console type EST /V and look at the RX overrun counter.
--- In Crestron@..., "innoventgroup" <innoventgroup@> wrote:
Ok.. I am totally baffeled. I have tried everything and cant seem to figure out what is causing the following errors.
System log:
1. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 02:54:41 3-12-13 UpTime: 0 days 02:11:18.91 Task: EnetLISR
2. Notice: Link established on LAN A
TimeStamp: 02:54:45 3-12-13 UpTime: 0 days 02:11:22.33 Task: PhyInitA
3. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:38:16 3-12-13 UpTime: 0 days 02:54:53.78 Task: EnetLISR
4. Notice: Link established on LAN A
TimeStamp: 03:38:20 3-12-13 UpTime: 0 days 02:54:57.54 Task: PhyInitA
5. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:38:22 3-12-13 UpTime: 0 days 02:54:59.26 Task: EnetLISR
6. Notice: Link established on LAN A
TimeStamp: 03:38:27 3-12-13 UpTime: 0 days 02:55:04.69 Task: PhyInitA
7. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:48:24 3-12-13 UpTime: 0 days 03:05:01.19 Task: EnetLISR
8. Notice: Link established on LAN A
TimeStamp: 03:48:27 3-12-13 UpTime: 0 days 03:05:04.62 Task: PhyInitA
9. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:49:28 3-12-13 UpTime: 0 days 03:06:05.01 Task: EnetLISR
10. Notice: Link established on LAN A
TimeStamp: 03:49:31 3-12-13 UpTime: 0 days 03:06:08.77 Task: PhyInitA
11. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:50:03 3-12-13 UpTime: 0 days 03:06:39.90 Task: EnetLISR
12. Notice: Link established on LAN A
TimeStamp: 03:50:07 3-12-13 UpTime: 0 days 03:06:43.66 Task: PhyInitA
This error continues to repeat (I think it is up to 120 times right now). Can anyone tell me what changed that is causig this? It seemed to start when I updated the system with a modification that had nothig to do with a lan connection. I have wireless broadband and they are updating it to a faster speed. The problem is that it goes on and off continually. These errors seem to correspond to this up and down access to the inet. Any suggestions?
Please Help,
DAVE
