This article is intended for administrators wishing to leverage StorMagic Edge Control in a secure networking environment.
Edge Control Secure Networking
Expand the sections below to review the Edge Control interface, architecture components, required internal and external ports, and connectivity testing commands.
Architecture Components
Edge Control Orchestrator
The Edge Control Orchestrator is a containerized application running on Ubuntu. StorMagic provides a pre-built OVA that can be downloaded from the Support Portal and deployed directly into the customer environment.
Alternatively, an Orchestrator can be deployed manually using the instructions below:
Deploying StorMagic Edge Control Orchestrator on a non-VMware Hypervisor
The containerized service communicates across the network to monitor and administer SvSAN VSAs, SvHCI nodes and SvSAN bare-metal nodes, securely forwarding telemetry to the Edge Control cloud service.
SvSAN VSAs
SvSAN VSAs are storage controller virtual machines deployed through the vCenter plugin. They are assigned storage devices and network interfaces to synchronously mirror, cache, encrypt and present storage over iSCSI.
Management traffic is exchanged between the plugin, VSAs, peer VSAs and Witness appliances alongside quorum communication.
Witness
SvSAN mirrored targets utilize a Witness appliance to provide quorum.
VSAs continuously heartbeat to the Witness and exchange cluster state information, allowing the platform to safely handle node and network failure scenarios.
Edge Orchestrator Required Internal Ports
| Service | Communication | Port | Protocol | Purpose |
|---|---|---|---|---|
| Management Service | Orchestrator → SvSAN VSAs / SvHCI Nodes | 8000 | TCP | Management, monitoring and administrative communication. |
| Discovery | Orchestrator ↔ StorMagic Devices / VSAs / Witness | 4174 | TCP / UDP |
Device discovery service. Discovery documentation |
| VM Management Service | Orchestrator → SvSAN VSAs / SvHCI Nodes | 443 | TCP | Virtual machine operations including power, migration and lifecycle management. |
Edge Orchestrator Required External Ports
| Service | Communication | Port | Protocol | Purpose |
|---|---|---|---|---|
| Orchestrator Service | Orchestrator → Edge Control Cloud | 443 | TCP |
Secure SSL/TLS communication used to transmit
monitoring and
management telemetry to the Edge Control cloud
service. https://manage.stormagic.com |
Testing Port Connectivity
Connectivity can be validated using common networking tools such as telnet or native Linux TCP testing.
Test connectivity by specifying the destination server name or IP address and the port number.
Using Telnet
telnet SERVERNAME/IP 8000Example:
telnet 10.10.0.15 8000Using Bash
On Linux systems, the following command can be used to test whether a TCP port is open:
(echo /dev/tcp/SERVERIP/8000) &/dev/null && echo "open 8000" || echo "close 8000"Example:
smadmin@svsan-plugin-vm:~$ (echo /dev/tcp/10.10.0.15/8000) &/dev/null && echo "open 8000" || echo "close 8000"
open 8000
smadmin@svsan-plugin-vm:~$ (echo /dev/tcp/10.10.0.11/8000) &/dev/null && echo "open 8000" || echo "close 8000"
close 8000
smadmin@svsan-plugin-vm:~$- Firewall rules blocking the required ports.
- Incorrect VLAN configuration.
- Routing issues between network segments.
- DNS resolution failures preventing communication with VSAs or services.
Comments
0 comments
Article is closed for comments.