DCE Private LAN Network Settings

[DCIM_Support]

Why are only IP and Subnet Mask configurable on the Private LAN?  Is it assumed that the devices are only on the same subnet, thus not needing a default gateway?  If so, how do I account for multiple subnets or being limited to 253 devices?

(CID:126182705)

[DCIM_Support]

Depending on your DCE server, you can configure the private lan to host up to 4000 devices by changing the subnet mask.  I'm pretty that the default gateway will just be .1 on your first network segment, you should be using DHCP on private lan A anyway, so your device will automatically have a default gateway.  You can use private network B for static ips.

I will note that the in my experience, the private lan is not intended to be used the same way a secondary network port is used on most servers, eg dual homing.  The private lan is instead intended a way to host a private network for your DCPI devices, similar to your how your home router works, this also saves IP space and makes it easy for these devices to grab an ip and be auto discovered.  In order to launch to devices on the private lan from the public lan, DHCP needs to be enabled.

If you're trying to use it as a second network port, I would advise not doing that and just put everything on your own network, and use only the DCE public lan.  You will be much happier in the long run. 
 

(CID:126182738)

[DCIM_Support]

Hi, Andrew.

It appears that you are suggesting that the DCE server be the DHCP server for the PRIVATE LAN Network A.  There is already a DHCP server on that network, managed by our Network Team.  The network where the managed devices reside (DCE PRIVATE LAN Network A interface) is also the network for other private management network devices, such as building automation tools.  Thus, the DCE server participates as a host on that network, not a network management server, not on a network limited to the DCE server.  Our managed devices exist on multiple subnets off of the PRIVATE LAN Network A interface.  The management traffic to and from the DCE needs to be routable and participate in the existing infrastructure.  Even 'Superscoping' the subnet mask does not help with the routing issue.

Our use of the PRIVATE nomenclature is to show that the devices off of that interface are not accessible from our regular business network, not that it is a standalone network for DCE.

The PRIVATE LAN Network A does not appear to be configurable to receive a Static DHCP address at either the DCE management interface window, or at the limited VM interface.

How can I get the DCE server to participate as a DHCP client on the PRIVATE LAN Network A interface, or how can I manage the IP Address, Subnet Mask and Default gateway settings for a static configuration on that interface.

The PUBLIC interface is working just fine and as intended.

(CID:126183062)

[DCIM_Support]

DCE does not accept DHCP on either interface, it's always static.  You can't manage IP, subnet mask AND gateway on either private lan a or b.  Again these aren't 2 individual NICs like a standard server, only the public Lan is.

So a little background, DCE use to only be a physical appliance, it had to 2 network interfaces, 1 on for the customers network and the private lan for its own, apc device network.  This was typically connected to an unmanaged APC switch.  It was never really intended to be connected to customers internal network.

When APC/Schneider virtualized the appliance, they kept the private lan option, but imo, it doesn't work very well in a virtualized environment.  Like I said before, the private lan isn't the same as a secondary nic.

As you've already found out, Private Lan A or B probably won't really work for what you're trying to accomplish.  

Based on this, I wouldn't recommend using the APC private lan at all.  Instead you should move the public lan interface to your private network and use that single interface.  If you need to access it from your public network, you will have to create a route to get to it, use a jump server, etc.  

I know this probably isn't the answer you want, but its how the DCE appliance has always worked and I highly doubt it will change anytime soon. 

 

(CID:126183107)

[DCIM_Support]

Hi, Andrew.

So it sounds like this is a limitation on the VM version of DCE.  Does the same limitation apply to the physical server version?  Can I multihome a physical server version of DCE running on top of an OS?

If not, then the only alternative would to put the DCE server and its PUBLIC Network behind a firewall on the building infrastructure network and disable the Private LAN.  Correct?

(CID:126183123)

[DCIM_Support]

Its a limitation of DCE, regardless if you have a physical or a VM,  I only mentioned the physical to provide a little background on how/why its like that.  No you cannot multi-home either version of DCE.

Yes, in instance I would recommend putting the PUBLIC network behind the firewall and disable the private lan.

(CID:126183139)

[DCIM_Support]

My network team would like to arrange a technical support conference call about network configuration options.  How is that arranged?

(CID:126184973)

[DCIM_Support]

You can contact your local APC by Schneider tech support team, if your'e in the US, they can be reached at 877-908-2688. 

(CID:126185129)

[DCIM_Support]

Dear Brady Burke,

From your question:

How can I get the DCE server to participate as a DHCP client on the PRIVATE LAN Network A interface, or how can I manage the IP Address, Subnet Mask and Default gateway settings for a static configuration on that interface.

This can not be done, because the DCE-server is distributed as a closed black box, which can not be changed.

With respect.

(CID:126183089)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.