Net2 Node Issues

We are just wrapping up correcting a host of troubles we had with our network that seem to have been related to incorrect firmware and a bad POE injector.  The system consists of an Obsession II single processor running 5.1.0, three 4 Port Nodes, 4 2 Port Nodes, a Video Node, and a dedicated PC for NCE.

We were advised to run the Version Detect and Upgrade Utility from NCE 4.0.3 to roll back the firmware on all of the nodes, which we did.  Currently all of the Nodes show a "Net Version" of 4.0.x (the exact version varies from node to node for some reason), but all of the 2 Ports show an "App Version" of 4.1.x (again exact version varies).  What exactly is the difference between "Net Version" and "App Version"?

Also, I would like help parsing an error message we received at one point when we had devices falling over left and right. If I remember correctly it was: [memory address] (tNetTask): arp info overwirtten for [second memory address] by [MAC address].  I apologize, I know it would be more helpful if I had the specific memory addresses and MAC addresses.  The first time this happened it was two devices (a four port and the video node) each trying to overwrite the same memory address.  Based on my limited understanding of ARP tables, my guess was they were each trying to claim the same IP address, though this was not how they were configured.  While this was repeatedly happening the system essentially ground to a halt.  After we had corrected the firmware on all the nodes and replaced the bad POE injector, we got the same address once more, again the video node, but it only happened once and we didn't see any loss of function or communication between any of the devices.  It appears to be a non-issue, but if someone from ETC could more clearly elaborate on what's happening when that system message appears I would feel much better.  Thank you.

Jim

Jim Gross
Assistant Production Manager
TheatreWorks
Palo Alto, CA

Parents
  • Can you copy the results of an arp -a command here?

  • So, it took a while to do this with one company moving our and another moving in but this is the arp table for the system:

    Interface: 10.101.1.101 --- 0x10003

    10.101.30.101  00-04-76-df-71-7f  dynamic

    10.101.40.101  00-c0-16-00-21-b5  dynamic

    10.101.50.111  00-c0-16-00-24-19  dynamic

    10.101.50.112  00-04-a1-00-04-dc  dynamic

    10.101.50.113  00-04-a1-00-05-f2  dynamic

    10.101.50.114  00-c0-16-00-24-01  dynamic

    10.101.50.115  00-04-a1-00-04-e2  dynamic

    10.101.50.116  00-c0-16-00-0d-1c  dynamic

    10.101.50.117  00-04-a1-00-05-fd  dynamic

    10.101.50.118  00-c0-16-00-24-39  dynamic

    10.101.50.201  00-04-a1-00-0f-13  dynamic

     

    In response to Derek's comment, NCE is the only device in the system with a DHCP server, and the address server was not on at the time of the error.  Actually, NCE wasn't running, it's only opened when configuring the input node (50.201).

     

    Jim

Reply
  • So, it took a while to do this with one company moving our and another moving in but this is the arp table for the system:

    Interface: 10.101.1.101 --- 0x10003

    10.101.30.101  00-04-76-df-71-7f  dynamic

    10.101.40.101  00-c0-16-00-21-b5  dynamic

    10.101.50.111  00-c0-16-00-24-19  dynamic

    10.101.50.112  00-04-a1-00-04-dc  dynamic

    10.101.50.113  00-04-a1-00-05-f2  dynamic

    10.101.50.114  00-c0-16-00-24-01  dynamic

    10.101.50.115  00-04-a1-00-04-e2  dynamic

    10.101.50.116  00-c0-16-00-0d-1c  dynamic

    10.101.50.117  00-04-a1-00-05-fd  dynamic

    10.101.50.118  00-c0-16-00-24-39  dynamic

    10.101.50.201  00-04-a1-00-0f-13  dynamic

     

    In response to Derek's comment, NCE is the only device in the system with a DHCP server, and the address server was not on at the time of the error.  Actually, NCE wasn't running, it's only opened when configuring the input node (50.201).

     

    Jim

Children
No Data
Related