Controller security against network hacking?
fogled@mizzou
h4x354x0r
Every so often, I get a spate of controller lockups across my campus (10+ Netlinx controllers), and the controller and panel has to be rebooted before the panel will come back online. Right now the controllers are all 'out of the box' condition in terms of security and passwords.
I suspect it's either our network group or a rogue student with access to our wired network doing invasive scanning / hacking. Is there a "best practice" for locking controllers down so they are reasonably secure against hackers? Or should I try to have our networking group firewall the device from everything but the panel and the local and my own remote subnet?
Thanks,
I suspect it's either our network group or a rogue student with access to our wired network doing invasive scanning / hacking. Is there a "best practice" for locking controllers down so they are reasonably secure against hackers? Or should I try to have our networking group firewall the device from everything but the panel and the local and my own remote subnet?
Thanks,
Comments
-
Does the master become unresponsive to IP - ie can you still Ping it or not? It might be worth checking your Buffers and Threshold values (& max values) as this is more likely to be the cause...
The other issue that shows up in this way is strong wireless interference - are you using MVP panels? If so it might be worth looking around with Netstumbler to see what activity is going on locally.
Surely the network admin, doesn't allow scanning of the network regardless. The password protection on the Masters is unlikly to foil a determined hacker, but it is definately worth deploying if randoms have access to the network, at least it will deter casual browsing of the masters web and telnet interfaces. -
In the instances I've been able to investigate (rather than having the controller power cycled to get a class or presentation going), I have not been able to ping the master. I've checked the buffer and threshold values on some controllers, but not the one I was dealing with today.
I am using one MVP8400 panel. I used to have it running from a discreet WAP, but was experiencing this problem. I finally removed the discreet WAP and got the panel set up on our campus wireless network, and the problem - at least on this system - went away for several months, but has come back. There's a microwave about 15 feet away from the equipment, but there shouldn't be much of anything else in terms of possible wireless interference. Oh, I haven't investigated for new cordless phone handsets yet, either.
I think I may be working at 2 different problems here:
One is a campus-wide, extremely intermittent controller lockup problem. The last time it happened was when our Networking group started a new scanning policy to find and eradicate "unauthorized" devices (discreet hubs, switches, and WAPs) from the network. But just late last week and early this week, I've seen a handful of controller lockups pop back up.
I think this one I'm working on today may have additional problems - likely what Jim noted above, or something similar along those lines, or possibly some other glitch coming from our network system.
Thanks for the tips! -
This thing is locking up all the time now. Can't connect or ping via IP, but I connected via serial OK. Can anyone help me understand what this all means? Here's the log:
---------------------------------------------------------------------------\par 1: 01-10-2031 FRI 15:59:25 Interpreter \par CIpEvent::OffLine 10001:1:1\par 2: 01-10-2031 FRI 15:59:25 ConnectionManager \par No Ping Response (s=1 d=10001) wait time=30000 mS\par 3: 01-10-2031 FRI 16:48:23 Interpreter \par CIpEvent::OffLine 32001:1:1\par 4: 01-10-2031 FRI 16:46:27 Interpreter \par CIpEvent::OnLine 32001:1:1\par 5: 01-10-2031 FRI 16:46:12 Interpreter \par CIpEvent::OffLine 32001:1:1\par 6: 01-10-2031 FRI 16:12:22 ConnectionManager \par Memory Available = 41632984 <57296>\par 7: 01-10-2031 FRI 16:10:50 ConnectionManager \par Memory Available = 41690280 <14400>\par 8: 01-10-2031 FRI 16:10:49 ConnectionManager \par Memory Available = 41704680 <11808>\par 9: 01-10-2031 FRI 16:10:47 ConnectionManager \par Memory Available = 41716488 <16064>\par 10: 01-10-2031 FRI 16:10:45 ConnectionManager \par Memory Available = 41732552 <77776>\par 11: 01-10-2031 FRI 16:10:37 ConnectionManager \par Memory Available = 41810328 <66208>\par 12: 01-10-2031 FRI 16:10:08 TelnetSvr \par Accepted Telnet connection:socket=32 addr=128.206.58.13 port=50634\par 13: 01-10-2031 FRI 16:09:37 Interpreter \par CIpEvent::OnLine 32001:1:1\par 14: 01-10-2031 FRI 16:04:46 ConnectionManager \par Memory Available = 41876536 <18480>\par 15: 01-10-2031 FRI 16:04:45 ConnectionManager \par Memory Available = 41895016 <25936>\par 16: 01-10-2031 FRI 16:04:35 ConnectionManager \par Memory Available = 41920952 <14816>\par 17: 01-10-2031 FRI 16:04:34 ConnectionManager \par Memory Available = 41935768 <160824>\par 18: 01-10-2031 FRI 16:04:31 ConnectionManager \par Memory Available = 42096592 <13528>\par 19: 01-10-2031 FRI 16:04:31 Unknown \par 16:04:31.749 EVENT Started HttpContext[/]\par 20: 01-10-2031 FRI 16:04:30 ConnectionManager \par Memory Available = 42110120 <79544>\par
BTW, I did reset the date / time in the controller. I have no idea how it got so wacked out. Could that contribute to the problem?
Thanks, -
Are you able to disconnect it from the main network and use a crossover cable to connect your computer directly to the processor? (You should have static IP address on both devices for this to be reliable) If this doesn't work, try disabling the program from running and see if it works afterward.
You might also want to try going into debug to see if it complains about the program tkn not matching. If that is the case, it's possible someone hijacked your processor
. With that thought in mind, I am not sure if you are doing it now, but I would advise not putting the code on the processor so it can't be extracted.
Just a couple thoughts,
Jeff -
Direct crossover network cable: not tried yet, but it's very unlikely. A reboot of the controller always brings everything back up. I'll try disabling the program as soon as I get another FAIL. Hasn't happened yet.
No complaints about non-matching tokens in Debug. That seems to work OK. I do have code stored on the master. In a big org like this, with me, others, and sometimes outside vendors working on systems, I've been bitten - totally hosed really - by not having the code stored on the master. I'll consider changing that practice, but I want to make sure I've always got good backups of the code somewhere. Any installs I've done in the last year, I've burnt a copy of the code to a CD whenever I change it, and slip the CD in a sleeve in the cabinet. But before that, and before I started doing the AMX programming, it was just luck and pluck whether or not I could even get code to do updates. -
Look at TN 544. I don't know if this is your problem, of course, but it should be easy to reset the masters to turn UDP off. There are a couple other tech notes which talk about problems with UDP.
I've only seen one problem like this and it was on a system that we were required to use the existing network. I think there were seven or eight masters linked up and one or more were locking up very frequently -- within ten minutes of being put on line. The situation was one of those with a tightly controlled network with managed Cisco switches and no real access to network configuration or information. Just about the only thing we could get from the network people was the IP addresses they wanted us to use and even that was a problem. Typical OCD network people. We tried everything we could think of without success but when we turned off UDP (after stumbling on TN544) we never saw the problem again. Not sure if that was what fixed it or not, but it's probably worth a test. -
Typical OCD network people.
That made me laugh out loud. Thank you for making my day. And here at MU, yes: not just OCD, but the emotional maturity of 10-year-olds.
And on a serious note, thanks for turning me on to the TN. That shoe fits my problem foot fairly well, I'll definitely wear it. -
-
Look at TN 544. I don't know if this is your problem, of course, but it should be easy to reset the masters to turn UDP off.
I can't find the actual "set udp bc rate" command in any references anywhere except that TN - not the NetLinx software history or the Netlinx Keywords help, or anywhere else. I would think this command would either go in the DEFINE_START or an ONLINE event for the master, but where is the best place to park this command?
thanks, -
The "set udp bc rate" command is only available in terminal/telnet. If it is noted in a manual, then in the corresponding master's operation manual.
The value you set is saved permanently, so it only has to be done once. -
Marc Scheibein wrote: »The "set udp bc rate" command is only available in terminal/telnet.
Oh... duh. Being a little bit dense of late.
FYI - I updated the master firmware on this unit from 3.21.something to the latest 3.30.371, and the device firmware from 1.12.140 to 1.13.7. So far, the system has not had any more problems since that firmware update. -
The panel seems to be staying online, but I still don't understand why it looks like the NSX Application keeps going offline and back online again. I have not updated the UDP broadcast setting yet, and don't entirely understand whether or not the buffers and threshold values are OK. Can anyone lend an eye to this log? It's the whole shebang since the reboot after the firmware upgrade. Thanks...
1 08-06-2008 WED 15:45:22 ConnectionManager Memory Available = 41615160 <15360> 2 08-06-2008 WED 15:45:18 ConnectionManager Memory Available = 41630520 <85168> 3 08-06-2008 WED 15:45:15 ConnectionManager Memory Available = 41715688 <80656> 4 08-06-2008 WED 15:45:14 ConnectionManager Memory Available = 41796344 <70152> 5 08-06-2008 WED 15:37:09 ConnectionManager Memory Available = 41866496 <10936> 6 08-06-2008 WED 15:34:58 Interpreter CIpEvent::OnLine 32001:1:1 7 08-06-2008 WED 15:34:58 ConnectionManager Memory Available = 41877432 <36064> 8 08-06-2008 WED 15:34:08 ConnectionManager Memory Available = 41913496 <34240> 9 08-06-2008 WED 15:33:08 ConnectionManager Memory Available = 41947736 <13536> 10 08-06-2008 WED 15:29:34 ConnectionManager Memory Available = 41961272 <39808> 11 08-06-2008 WED 15:29:20 ConnectionManager Memory Available = 42001080 <18080> 12 08-06-2008 WED 15:29:19 ConnectionManager Memory Available = 42019160 <110984> 13 08-06-2008 WED 15:29:18 ConnectionManager Memory Available = 42130144 <75968> 14 08-06-2008 WED 15:29:10 ConnectionManager Memory Available = 42206112 <82520> 15 08-06-2008 WED 15:29:09 ConnectionManager Memory Available = 42288632 <110448> 16 08-06-2008 WED 15:29:08 ConnectionManager Memory Available = 42399080 <10384> 17 08-06-2008 WED 12:51:23 Interpreter CIpEvent::OffLine 32001:1:1 18 08-06-2008 WED 09:28:54 Interpreter CIpEvent::OnLine 32001:1:1 19 08-06-2008 WED 09:13:16 Interpreter CIpEvent::OffLine 32001:1:1 20 08-05-2008 TUE 16:59:08 Interpreter CIpEvent::OnLine 32001:1:1 21 08-05-2008 TUE 15:14:17 Interpreter CIpEvent::OffLine 32001:1:1 22 08-05-2008 TUE 15:14:17 ConnectionManager No Ping Response (s=1 d=32001) wait time=30000 mS 23 08-05-2008 TUE 13:51:39 Interpreter CIpEvent::OnLine 32001:1:1 24 08-05-2008 TUE 13:22:42 Interpreter CIpEvent::OffLine 32001:1:1 25 08-05-2008 TUE 13:22:35 Interpreter CIpEvent::OnLine 32001:1:1 26 08-05-2008 TUE 13:22:11 Interpreter CIpEvent::OffLine 32001:1:1 27 08-05-2008 TUE 13:21:23 Interpreter CIpEvent::OnLine 32001:1:1 28 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:17:1 29 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:16:1 30 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:15:1 31 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:14:1 32 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:13:1 33 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:12:1 34 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:11:1 35 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:10:1 36 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:9:1 37 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:8:1 38 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:7:1 39 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:6:1 40 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:5:1 41 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:4:1 42 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:3:1 43 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:2:1 44 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OnLine 5001:1:1 45 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:17:1 46 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:16:1 47 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:15:1 48 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:14:1 49 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:13:1 50 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:12:1 51 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:11:1 52 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:10:1 53 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:9:1 54 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:8:1 55 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:7:1 56 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:6:1 57 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:5:1 58 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:4:1 59 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:3:1 60 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:2:1 61 08-05-2008 TUE 13:21:07 Interpreter CIpEvent::OffLine 5001:1:1 62 08-05-2008 TUE 13:21:05 Interpreter CIpEvent::OffLine 32001:1:1 63 08-05-2008 TUE 13:20:31 ConnectionManager Memory Available = 42409464 <32784> 64 08-05-2008 TUE 13:20:30 Interpreter CIpEvent::OnLine 32001:1:1 65 08-05-2008 TUE 13:20:13 Interpreter CIpEvent::OffLine 32001:1:1 66 08-05-2008 TUE 13:20:11 ConnectionManager Memory Available = 42442248 <20480> 67 08-05-2008 TUE 13:20:11 Unknown IPDeviceDetector.run(): joined multicast group 68 08-05-2008 TUE 13:20:10 Interpreter CIpEvent::OnLine 32001:1:1 69 08-05-2008 TUE 13:20:10 ConnectionManager Memory Available = 42462728 <41056> 70 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 10001:1:1 71 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:17:1 72 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:16:1 73 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:15:1 74 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:14:1 75 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:13:1 76 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:12:1 77 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:11:1 78 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:10:1 79 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:9:1 80 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:8:1 81 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:7:1 82 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:6:1 83 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:5:1 84 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:4:1 85 08-05-2008 TUE 13:20:09 Unknown (Reader=tInterpreter writer=tDeviceMgr)- CMessagePipe::Max = 50 86 08-05-2008 TUE 13:20:09 Unknown (Reader=tInterpreter writer=tDeviceMgr)- CMessagePipe::Max = 25 87 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:3:1 88 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:2:1 89 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 5001:1:1 90 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 0:1:1 91 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 33005:1:1 92 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 33003:1:1 93 08-05-2008 TUE 13:20:09 Interpreter CIpEvent::OnLine 33006:1:1 94 08-05-2008 TUE 13:20:09 ConnectionManager Memory Available = 42503784 <241352> 95 08-05-2008 TUE 13:20:09 Interpreter CIpInterpreter::Run - Execute Startup Code 96 08-05-2008 TUE 13:20:09 Unknown 13:20:09.199 EVENT Started org.mortbay.jetty.Server@72c4f8 97 08-05-2008 TUE 13:20:09 Unknown 13:20:09.199 EVENT Started SocketListener on 0.0.0.0:80 98 08-05-2008 TUE 13:20:08 Unknown 13:20:08.966 EVENT Starting Jetty/4.2.x 99 08-05-2008 TUE 13:20:08 Unknown DynamicServlet 0.0.1 has been started 100 08-05-2008 TUE 13:20:08 Unknown 13:20:08.916 EVENT Started ServletHttpContext[/] 101 08-05-2008 TUE 13:20:08 ConnectionManager Memory Available = 42745136 <90240> 102 08-05-2008 TUE 13:20:08 Unknown SecurityServlet 0.0.1 has been started 103 08-05-2008 TUE 13:20:08 Unknown 13:20:08.433 EVENT Started ServletHttpContext[/] 104 08-05-2008 TUE 13:20:07 Unknown ConfigServlet 0.0.1 has been started 105 08-05-2008 TUE 13:20:07 Unknown 13:20:07.766 EVENT Started ServletHttpContext[/] 106 08-05-2008 TUE 13:20:07 ConnectionManager Memory Available = 42835376 <354440> 107 08-05-2008 TUE 13:20:07 Unknown DeviceServlet 0.0.1 has been started 108 08-05-2008 TUE 13:20:07 Unknown 13:20:07.216 EVENT Started ServletHttpContext[/] 109 08-05-2008 TUE 13:20:06 ConnectionManager Memory Available = 43189816 <89704> 110 08-05-2008 TUE 13:20:06 Unknown RootServlet 0.0.1 has been started 111 08-05-2008 TUE 13:20:06 Unknown 13:20:06.733 EVENT Started ServletHttpContext[/] 112 08-05-2008 TUE 13:20:06 Unknown 13:20:06.216 EVENT Started ServletHttpContext[/] 113 08-05-2008 TUE 13:20:06 ConnectionManager Memory Available = 43279520 <15232> 114 08-05-2008 TUE 13:20:06 Unknown 13:20:05.549 EVENT Started ServletHttpContext[/] 115 08-05-2008 TUE 13:20:05 ConnectionManager Memory Available = 43294752 <55552> 116 08-05-2008 TUE 13:20:04 ConnectionManager Memory Available = 43350304 <200408> 117 08-05-2008 TUE 13:20:03 ConnectionManager Memory Available = 43550712 <30896> 118 08-05-2008 TUE 13:20:02 ConnectionManager Memory Available = 43581608 <262472> 119 08-05-2008 TUE 13:20:02 Unknown DynamicDeviceDetector 0.0.1 has been started 120 08-05-2008 TUE 13:20:01 ConnectionManager Memory Available = 43844080 <168064> 121 08-05-2008 TUE 13:20:01 Unknown DeviceAccess 0.0.1 has been started 122 08-05-2008 TUE 13:20:01 ConnectionManager Memory Available = 44012144 <43288> 123 08-05-2008 TUE 13:19:59 ConnectionManager Memory Available = 44055432 <84728> 124 08-05-2008 TUE 13:19:59 Unknown DeviceManager 0.0.1 has been started 125 08-05-2008 TUE 13:19:58 ConnectionManager Memory Available = 44140160 <218504> 126 08-05-2008 TUE 13:19:58 ConnectionManager Memory Available = 44358664 <10440> 127 08-05-2008 TUE 13:19:57 ConnectionManager Memory Available = 44369104 <12256> 128 08-05-2008 TUE 13:19:57 ConnectionManager Memory Available = 44381360 <10336> 129 08-05-2008 TUE 13:19:57 ConnectionManager Memory Available = 44391696 <17416> 130 08-05-2008 TUE 13:19:57 ConnectionManager Memory Available = 44409112 <242944> 131 08-05-2008 TUE 13:19:56 ConnectionManager Memory Available = 44652056 <54056> 132 08-05-2008 TUE 13:19:55 ConnectionManager Memory Available = 44706112 <22752> 133 08-05-2008 TUE 13:19:55 ConnectionManager Memory Available = 44728864 <77376> 134 08-05-2008 TUE 13:19:54 ConnectionManager Memory Available = 44806240 <34624> 135 08-05-2008 TUE 13:19:54 ConnectionManager Memory Available = 44840864 <15232> 136 08-05-2008 TUE 13:19:54 Unknown Create Jetty Web Server 137 08-05-2008 TUE 13:19:54 ConnectionManager Memory Available = 44856096 <78008> 138 08-05-2008 TUE 13:19:53 ConnectionManager Memory Available = 44934104 <53408> 139 08-05-2008 TUE 13:19:52 ConnectionManager Memory Available = 44987512 <105088> 140 08-05-2008 TUE 13:19:52 ConnectionManager Memory Available = 45092600 <212552> 141 08-05-2008 TUE 13:19:51 ConnectionManager Memory Available = 45305152 <20864> 142 08-05-2008 TUE 13:19:51 Unknown ================= 143 08-05-2008 TUE 13:19:51 Unknown Welcome to Duet. 144 08-05-2008 TUE 13:19:51 ConnectionManager Memory Available = 45326016 <20032> 145 08-05-2008 TUE 13:19:50 ConnectionManager Memory Available = 45346048 <517128> 146 08-05-2008 TUE 13:19:49 ConnectionManager Memory Available = 45863176 <3630008> 147 08-05-2008 TUE 13:19:49 InternalMessageRouter Preparing to initialize java.lang.Thread 148 08-05-2008 TUE 13:19:49 Unknown (0000007575) Preparing to initialize java.lang.Thread 149 08-05-2008 TUE 13:19:49 InternalMessageRouter Preparing to initialize java.lang.ClassLoader$NativeLibrary 150 08-05-2008 TUE 13:19:49 Unknown (0000007574) Preparing to initialize java.lang.ClassLoader$NativeLibrary 151 08-05-2008 TUE 13:19:49 InternalMessageRouter Preparing to initialize java.lang.ClassLoader 152 08-05-2008 TUE 13:19:49 Unknown (0000007573) Preparing to initialize java.lang.ClassLoader 153 08-05-2008 TUE 13:19:49 InternalMessageRouter Preparing to initialize java.lang.Shutdown 154 08-05-2008 TUE 13:19:49 Unknown (0000007572) Preparing to initialize java.lang.Shutdown 155 08-05-2008 TUE 13:19:49 InternalMessageRouter Preparing to initialize sun.misc.ThreadRegistry 156 08-05-2008 TUE 13:19:49 Unknown (0000007572) Preparing to initialize sun.misc.ThreadRegistry 157 08-05-2008 TUE 13:19:49 InternalMessageRouter Preparing to initialize java.lang.String 158 08-05-2008 TUE 13:19:49 Unknown (0000007571) Preparing to initialize java.lang.String 159 08-05-2008 TUE 13:19:49 InternalMessageRouter Preparing to initialize java.lang.Float 160 08-05-2008 TUE 13:19:49 Unknown (0000007570) Preparing to initialize java.lang.Float 161 08-05-2008 TUE 13:19:49 InternalMessageRouter Preparing to initialize java.lang.Class 162 08-05-2008 TUE 13:19:49 Unknown (0000007568) Preparing to initialize java.lang.Class 163 08-05-2008 TUE 13:19:49 Unknown JVM Logger Thread Started 164 08-05-2008 TUE 13:19:47 ConnectionManager Memory Available = 49493184 <11280> 165 08-05-2008 TUE 13:19:46 ConnectionManager Memory Available = 49504464 <486536> 166 08-05-2008 TUE 13:19:44 ConfigurationManager Extracting Morpheus files 167 08-05-2008 TUE 13:19:44 Interpreter CIpUffHandler::Load - NV Ram Used 36632 168 08-05-2008 TUE 13:19:44 Interpreter CIpUffHandler::Load - NV Ram Total 1047536 169 08-05-2008 TUE 13:19:44 Interpreter CIpUffHandler::Load Good Incoming was 37% of Actual Size 120KB 170 08-05-2008 TUE 13:19:44 Interpreter CIpSymbol::LoadModuleInfo 18 0 171 08-05-2008 TUE 13:19:44 Interpreter CIpBreak::LoadBreakPointInfo 39198 780 172 08-05-2008 TUE 13:19:44 Interpreter CIpSymbol::LoadStackParaInfo 2924 70 173 08-05-2008 TUE 13:19:44 Interpreter CIpSymbol::LoadGlobalLocalInfo 10472 264 174 08-05-2008 TUE 13:19:44 Interpreter CIpSymbol::LoadFunctionInfo 1064 33 175 08-05-2008 TUE 13:19:44 Interpreter CIpSymbol::LoadStructureInfo 1110 10 176 08-05-2008 TUE 13:19:44 Interpreter CIpSymbol::LoadFileInfo 358 6 177 08-05-2008 TUE 13:19:44 Interpreter CIpTempMan::LoadTemplate 8546 1 178 08-05-2008 TUE 13:19:44 Interpreter CIpDeviceList::LoadDeviceList 878 1 179 08-05-2008 TUE 13:19:44 Interpreter CIpMutual::LoadList 486 180 08-05-2008 TUE 13:19:44 Interpreter CIpCodeMan::LoadTable 14 1 181 08-05-2008 TUE 13:19:44 Interpreter CIpDirect::LoadDirect 2496 1 182 08-05-2008 TUE 13:19:44 Interpreter CIpListMan::LoadNonVolatile Restore 1 183 08-05-2008 TUE 13:19:44 Interpreter CIpListMan::LoadVolatile 11484 1 184 08-05-2008 TUE 13:19:44 Interpreter CIpCodeMan::LoadCode 41626 1 185 08-05-2008 TUE 13:19:44 Interpreter CIpUffHandler::Module Header 186 08-05-2008 TUE 13:19:44 Interpreter CIpUffHandler::Project Name=PCC_v4 187 08-05-2008 TUE 13:19:44 Interpreter CIpUffHandler::Root 188 08-05-2008 TUE 13:19:44 Interpreter CIpUffHandler::Load - Begin...doc:PROG.TKN 189 08-05-2008 TUE 13:19:44 Interpreter CIpNvMemory::NvInitalize NvRam Tested OK Used=36632 Available=1010904 190 08-05-2008 TUE 13:19:44 Interpreter CIpInterpreter::Run - Unlocking Interpreter Mutex Early (Device Hold off is off) 191 08-05-2008 TUE 13:19:44 ConnectionManager Memory Available = 49939448 192 08-05-2008 TUE 13:19:43 ConfigurationManager JVMStartParam(2): -Djava.security.manager -Doscar.profile.name=Duet org.ungoverned.oscar.Main 193 08-05-2008 TUE 13:19:43 ConfigurationManager JVMStartParam(1): v1.1 runJava -XsafeExit -Xms3M -Dpath.separator=; -Djava.class.path=doc:/lib;doc:/lib/Oscar.jar 194 08-05-2008 TUE 13:19:43 ConfigurationManager UDP Blink Message Time = 5 seconds (0=off) 195 08-05-2008 TUE 13:19:43 ConfigurationManager Log Entry Count = 1000 196 08-05-2008 TUE 13:19:42 ConfigurationManager TCP Timeout = 45000mS 197 08-05-2008 TUE 13:19:42 ConfigurationManager NetLinx Sockets Message Queue Size = 50 198 08-05-2008 TUE 13:19:42 ConfigurationManager PhastLink Receive Message Queue Size = 500 199 08-05-2008 TUE 13:19:42 ConfigurationManager ICSNet Receive Message Queue Size = 200 200 08-05-2008 TUE 13:19:42 ConfigurationManager LontalkHost Message Queue Size = 500 201 08-05-2008 TUE 13:19:42 ConfigurationManager Lontalk Message Queue Size = 500 202 08-05-2008 TUE 13:19:42 ConfigurationManager UDP Transmit Message Queue Size = 500 203 08-05-2008 TUE 13:19:42 ConfigurationManager ICSP 232 Transmit Message Queue Size = 500 204 08-05-2008 TUE 13:19:42 ConfigurationManager ICSNet Transmit Message Queue Size = 500 205 08-05-2008 TUE 13:19:42 ConfigurationManager PhastLink Transmit Message Queue Size = 500 206 08-05-2008 TUE 13:19:42 ConfigurationManager Axlink Transmit Message Queue Size = 800 207 08-05-2008 TUE 13:19:42 ConfigurationManager Message Dispatcher Message Queue Size = 1000 208 08-05-2008 TUE 13:19:42 ConfigurationManager IP Connection Manager Message Queue Size = 800 209 08-05-2008 TUE 13:19:42 ConfigurationManager TCP Transmit Threads Message Queue Size = 600 210 08-05-2008 TUE 13:19:42 ConfigurationManager Diagnostic Manager Message Queue Size = 500 211 08-05-2008 TUE 13:19:42 ConfigurationManager Device Manager Message Queue Size = 1500 212 08-05-2008 TUE 13:19:42 ConfigurationManager Route Manager Message Queue Size = 400 213 08-05-2008 TUE 13:19:42 ConfigurationManager Connection Manager Message Queue Size = 2000 214 08-05-2008 TUE 13:19:42 ConfigurationManager Notification Manager Message Queue Size = 2000 215 08-05-2008 TUE 13:19:42 ConfigurationManager Interpreter Message Queue Size = 2000 216 08-05-2008 TUE 13:19:42 ConfigurationManager Routing Flags = $0 217 08-05-2008 TUE 13:19:42 ConfigurationManager AMX URL = www.amx.com 218 08-05-2008 TUE 13:19:42 ConfigurationManager CRL Check level = 0 219 08-05-2008 TUE 13:19:42 ConfigurationManager IPSec Enabled = 0 220 08-05-2008 TUE 13:19:42 ConfigurationManager Timeline Loopcnt = 10 221 08-05-2008 TUE 13:19:42 ConfigurationManager IP Threshold = 1500 222 08-05-2008 TUE 13:19:42 ConfigurationManager Lontalk Threshold = 50 223 08-05-2008 TUE 13:19:42 ConfigurationManager Interpreter Threshold = 1500 224 08-05-2008 TUE 13:19:42 ConfigurationManager Device Holdoff = 0 225 08-05-2008 TUE 13:19:42 ConfigurationManager URL Entry Count = 0 226 08-05-2008 TUE 13:19:42 ConfigurationManager DNS Entry Count = 0 227 08-05-2008 TUE 13:19:42 ConfigurationManager Domain Name = 228 08-05-2008 TUE 13:19:42 ConfigurationManager Serial Number = '210505x0970272' 229 08-05-2008 TUE 13:19:42 ConfigurationManager System = 1 230 08-05-2008 TUE 13:19:42 ConfigurationManager LoadConfiguration Complete (26920).
-
NetLinx Studio (NSX) is not permanently connected with the system. It is just connecting i.e. when starting a file transfer, load the online tree, etc. It is online for longer period if you let run notification, diagnostics and/or the debugger. A touchpanel would come online when it has booted (or it is booted and the master has been restarted). A wired panel in normal case would not go offline at any time, a wireless panel may be detected as offline when it has reached the shutdown time (or the battery is empty
), or it looses Wifi connect for longer time (about 45 seconds).
One more word to the UDP broadcast.
The broadcast is only required if you run a panel in System Setting Mode "Auto".
Auto: panel listens to master UDP broadcast messages, and will connect to a master if the system number set in the system settings matches
URL: panel directly tries to connect to the master URL defined, system number in panel is not considered
Listen: master must try (by an URL list entry) to connect to a panel's url, system number in panel is not considered
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums