Reply To: NAT with 9300-ENA

#3146
Cajun Configurator
Sean Terrell
Moderator
  • Topics: 6
  • Replies: 29
  • Total Posts: 35
Karma: 184
Rank: Jedi

PM’d you on linkedin with link to drawings. I dont really want to post them… Im not sure how the company (mine) or the customer would like that?

Ok so yes..Kind of.

The IP schema works like this. Internal “control” network = 192.168.1.xx where xx = the same device on every pad. 192.168.1.10 = MCC Site Control PLC, 192.168.1.4 = Red Lion DSPX (for measurement), .11 MCC PLC, .5 Flow Computer…. ect. What ever equipment is on the site Gas Lift Compressor PLC # 1 = .241, HMI .240 any pad in this area are all built the same like this.

Then we have a separate network that is Public IP’s and is not controls just SCADA. there are only a couple of devices on each pad with direct access to the SCADA side. There are more than 500 sites over 5 counties. Each county has a gateway and all of the radios in that area direct the traffic there, then back into the wired office network.

All of them are 172. addresses. then .20, 24,26 the second octet is the county.

County 1 all addresses are 172.20.xx.xx. County 2 is 172.24.xx.xx

the third octet is the specific “pad” identifier.So  hes a 172.24.60.xx says county 2 pad 60.

then the final octet is the device. so the MCC PLC has a 2nd EBNT that is 172.24.60.21. The red lion DSPX has a 2nd ethernet card that is 172.24.60.31. a second red Lion DSPX is 172.24.60.4 that port forwards to the flowcomputer.

Ok Following that? internal network. 192. External 172. The external network goes from the MCC to a panel with a stratix 8K and then a radio on the pole.

All of the external devices. All of them. EVERY ONE of them, its does not work unless, you give them a gateway of 172.24.0.1 or 172.20.0.1 or 176.0.1 with a netmask of 255.252.0.0 However the NAT IP has no gateway.