EcoStruxure IT forum
Schneider Electric support forum about installation and configuration for DCIM including EcoStruxure IT Expert, IT Advisor, Data Center Expert, and NetBotz
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-06-11 05:07 PM
Hi, so I just want to get this clear as it isn't intuitive for me. Struxureware has an A network that is routable, and a B network that is not routable. I have devices on say, 10.0.5.0/24 and more devices on 10.0.6.0/22 plus my management network which is 192.168.0.0/24.
How would I go about configuring Struxureware to reach all my devices, and be able to manage it?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-06-12 05:07 AM
Hello @schneider-electric-user-99,
The intended use of the Data Center Expert private network is to be a completely isolated network only connected to Data Center Expert's private network port. This isolates the devices to connections only being allowed through Data Center Expert for certain functions.
If today you have multiple networks that you computer has access to through 1 corporate network connection, then the devices / network is not currently designed for using the Data Center Expert private network as your network is set up to be routable between all of those different networks using VLANs or other routing / access rules.
Here is an example of a simple private network setup as intended:
Within this network your 10.X.X.X networks are connected to the public DCE port and DCE is able to route that traffic to its defined public gateway for your network configuration to route accordingly.
The Private Network of DCE is intended to be fully isolated from corporate connections as the devices gateways would need to be set to DCE's private IP address to ensure that communicate comes back on the correct interface.
When using the private network, there are clear limitations to what can and can't be done as all communication must be initiated through the DCE desktop client if you must do something on the device directly. This limits you to what can be done primarily with the web interface only and no other connections.
If you would like full access to devices on the private side of DCE, you would need to have all devices connected through the public interface and control access / routing at the switch/router level or higher by utilizing routing rules / firewalls / ACLs / etc.
Your computer and other private side devices should have no access to those devices on the private side of DCE, if they do, it would be best to not utilize the private network and set it to an IP address range/scheme that is not consumed on your private network.
In summary, DCE's private network is designed to be a fully isolated network that is only accessible through DCE and not directly by anything outside of the private network. If you would like direct access to devices without going through DCE, all devices/traffic must be on the public network and you can control access to access / routing to that through the devices on your public side network.
Please let me know if you have any additional questions or need clarification on any of the above.
Kind Regards,
Cory
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-06-12 05:07 AM
Hello @schneider-electric-user-99,
The intended use of the Data Center Expert private network is to be a completely isolated network only connected to Data Center Expert's private network port. This isolates the devices to connections only being allowed through Data Center Expert for certain functions.
If today you have multiple networks that you computer has access to through 1 corporate network connection, then the devices / network is not currently designed for using the Data Center Expert private network as your network is set up to be routable between all of those different networks using VLANs or other routing / access rules.
Here is an example of a simple private network setup as intended:
Within this network your 10.X.X.X networks are connected to the public DCE port and DCE is able to route that traffic to its defined public gateway for your network configuration to route accordingly.
The Private Network of DCE is intended to be fully isolated from corporate connections as the devices gateways would need to be set to DCE's private IP address to ensure that communicate comes back on the correct interface.
When using the private network, there are clear limitations to what can and can't be done as all communication must be initiated through the DCE desktop client if you must do something on the device directly. This limits you to what can be done primarily with the web interface only and no other connections.
If you would like full access to devices on the private side of DCE, you would need to have all devices connected through the public interface and control access / routing at the switch/router level or higher by utilizing routing rules / firewalls / ACLs / etc.
Your computer and other private side devices should have no access to those devices on the private side of DCE, if they do, it would be best to not utilize the private network and set it to an IP address range/scheme that is not consumed on your private network.
In summary, DCE's private network is designed to be a fully isolated network that is only accessible through DCE and not directly by anything outside of the private network. If you would like direct access to devices without going through DCE, all devices/traffic must be on the public network and you can control access to access / routing to that through the devices on your public side network.
Please let me know if you have any additional questions or need clarification on any of the above.
Kind Regards,
Cory
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.