Diagnostics message unclear....
markbsure
Posts: 44
Line 82 :: ICSPTCPRx31: Ignoring msg from foreign device (same DPS) (IP=0xC0A80134) Cmd=2 DSys=1 DDev=0 TCP Socket=31 IP=192.168.1.52 Index=1 - 11:34:03
Line 83 :: Routing Loop detected. Killing route to system 1. - 11:34:03
Line 84 :: ICSPTCPRx30: Ignoring msg from foreign device (same DPS) (IP=0xC0A80133) Cmd=2 DSys=1 DDev=0 TCP Socket=30 IP=192.168.1.51 Index=0 - 11:34:06
Line 85 :: Routing Loop detected. Killing route to system 1. - 11:34:07
Line 86 :: ICSPTCPRx31: Ignoring msg from foreign device (same DPS) (IP=0xC0A80134) Cmd=2 DSys=1 DDev=0 TCP Socket=31 IP=192.168.1.52 Index=1 - 11:34:07
Line 87 :: Routing Loop detected. Killing route to system 1. - 11:34:07
the above is copied out of my diagnostics window. these messages seem to appear now and again, and im unsure why they do. they don't seem to adversely affect the system, but i'd like to know if there is a problem....
the AMX system is an NI-3100 as master and running all code (diagnostics was taken from this processor), with two NI-900's connected via IP which contain no code, and are just used as extra control ports.
NI-3100: IP = 192.168.1.50, Device 1, System 1
NI-900 1: IP = 192.168.1.51, Device 1, System 2
NI-900 2: IP = 192.168.1.52, Device 1, System 3
The URL listing table is only present in the NI-3100 and only contains the IP addresses of the two NI-900s.
Can anyone shed any light?
mark
Line 83 :: Routing Loop detected. Killing route to system 1. - 11:34:03
Line 84 :: ICSPTCPRx30: Ignoring msg from foreign device (same DPS) (IP=0xC0A80133) Cmd=2 DSys=1 DDev=0 TCP Socket=30 IP=192.168.1.51 Index=0 - 11:34:06
Line 85 :: Routing Loop detected. Killing route to system 1. - 11:34:07
Line 86 :: ICSPTCPRx31: Ignoring msg from foreign device (same DPS) (IP=0xC0A80134) Cmd=2 DSys=1 DDev=0 TCP Socket=31 IP=192.168.1.52 Index=1 - 11:34:07
Line 87 :: Routing Loop detected. Killing route to system 1. - 11:34:07
the above is copied out of my diagnostics window. these messages seem to appear now and again, and im unsure why they do. they don't seem to adversely affect the system, but i'd like to know if there is a problem....
the AMX system is an NI-3100 as master and running all code (diagnostics was taken from this processor), with two NI-900's connected via IP which contain no code, and are just used as extra control ports.
NI-3100: IP = 192.168.1.50, Device 1, System 1
NI-900 1: IP = 192.168.1.51, Device 1, System 2
NI-900 2: IP = 192.168.1.52, Device 1, System 3
The URL listing table is only present in the NI-3100 and only contains the IP addresses of the two NI-900s.
Can anyone shed any light?
mark
0
Comments
Do you have rebooted the masters after setting the system numbers?
You can check that for example by terminal/telnet with the SHOW DEVICE command:
So my system here has system number #2.
I am sure all the processors are set to different system numbers. The system numbers were set when i first installed the equipment, and all processors have been rebooted many times during the programming of the system! The code running in the master NI-3100 references the two NI-900 ports with their respective system numbers (2 and 3) and works fine.
when i next get back on site i will double check this via telnet, but I'm pretty sure the system numbers are correct.
I have the WHC control master which is system 1 pointing to the others:
Here is my url list
getting this error message
Any ideas???
You may have a URL setup from the main master (system 1) to the 2 secondary masters (systems 2,3) and then systems 2,3 back to the main master.
You only need to do an URL from the 2 secondary masters to the main one. That sets up the two-way communication from all three masters.
To state it another way, you do not need to enter in any URL link from the main system master (system 1)
This error is most likely NOT becuase of your master to master setup. I once had this problem aswell. What's causing the error is you have an event (most likely a level event) that gets sent to one master. Triggers and event there. Then info gets sent back to the original master, triggers and event there. The orignal master then triggers an event back to the remote master... etc... Bascially, an Infinite loop starts. Level Events are usually the main cause of this. Comment Out some level events on one of your masters until you find the event causing the inifinite loop. Then figure out how to prevent it.