The table below illustrates the relationship between messages and their corresponding configuration addresses.
Table 5.1 Message Routing
ENI receives read or | ENI TCP/IP route | Message forwarded to destination |
write PCCC message to | configuration | node TCP/IP address |
|
|
|
Node 0 | Node100 | 111.222.233.200 (stored at Node 100) |
|
|
|
Node 1 | Node101 | 111.222.233.201 (stored at Node 101) |
|
|
|
| When the ENI receives a PCCC write message to a | |
IMPORTANT | ||
configuration node address (100 through 149), it | ||
| ||
| ||
| closes any open communications currently active on | |
| that connection and reconfigures the IP address to | |
| match the new configuration. |
If the received data matches the current configuration, the ENI closes any open communications with the destination device.
If the ENI receives a PCCC read message to any of its configuration addresses (nodes 100 to 149), the ENI responds with the current configuration of that node/address.
Using the configuration shown in Table
Publication