CLX 5000 Eth routing

[pahuffman]

So I am trying to route through a ControlLogix chassis to a CompactLogix and I am running in to trouble.  Trying to get to internal PLC from outside network.
 Setup looks like this:
Bridge chassis
  Outside ENBT slot 5 10.60.88.154
  Internal ENBT slot 4 192.168.1.1
  Target PLC 192.168.1.71

I have tried using various version of the RoutePath with the following results
1, 4, 2, 192.168.1.71, 1, 0    No Response from PLC 10.60.88.154, slot=0
1, 4, 2, 192.168.1.71, 1, 1    No Response from PLC 10.60.88.154, slot=0
1, 4, 2, 192.168.1.71    No Response from PLC 10.60.88.154, slot=0
1,4,2,192.168.1.71     Path Segment Error (Invalid Tag Name)

I am using a MSG on this host PLC using the same route and it works fine.  I know with CompactLogix you don't use the routing to the backplane and the PLC slot.  Am I missing something obvious?  Thanks in advance.

[Archie]

The first route should be correct. Not sure why #4 gives a response, but #3 does not. Seems to not like the spaces. #4 is stopping at the Ethernet port and that would be the reason for the Path Segment error. With that I would try:

1,4,2,192.168.1.71,1,0

[bachphi]

make sure to set gateway on each ENBT card

[pahuffman]

Thanks for the rapid response, that was faster then RA TechConnect sometimes!  I thought the first one would work as well.  I do notice when I look at the path in RSLogix it calls out the backplane and PLC port on the target machine.  It is listed as "Cutting\10.60.88.154\Backplane\4\A\192.68.1.71\Backplane\0".

Interesting side note, if I replace "1" with the word "Backplane" and "2'" with the letter "A", it responds the same.

**Edit**
It is a routing issue for sure somehow.  I tried to get to another ControlLogix behind the same bridge and got the same results.  I am able to read date from the bridge PLC directly.  The ProcessorSlot value should remain 0 correct?

[Archie]

If you have a value in RoutePath then ProcessorSlot is not used. The last number in the route path would be the processor slot.

Would you be able to run a Wireshark capture? This may give a clue as to what is happening.

[pahuffman]

12210   512.275055   10.60.88.57   10.60.93.33   CIP CM   110   Connection failure: Connection Manager - Forward Open
12218   512.480265   10.60.93.33   10.60.88.57   TCP   54   54360 → 44818 [ACK] Seq=9541 Ack=5041 Win=4854 Len=0
12489   519.593731   10.60.93.33   10.60.88.57   CIP CM   160   Connection Manager - Forward Open (Message Router)

Is what I see in this conversation.  I am not knowledgeable at all with WireShark, so not sure if this helps.

[Archie]

The details of most importance is the packet of the Forward Open. Wireshark will let you drill into the packet details. You want to look for the route to make sure the driver parses the RoutePath correctly.