Fimer FMR-PVS-10-TL-SX, Руководство по эксплуатации продукта

Страница: 78 / 80

EN
78
9. Attachments
9.1 Port and network services used by the inverter
9.1.1 IP Network Services
Any network connected to the inverter must allow traffic to pass on the following ports. Network firewall rules (if present) must allow
responses to the inverter over existing TCP connections.
Direction Service/Port Protocol Description
In ssh/22 Tcp
For local debugging by FIMER service personnel, the inverter utilizes encrypted
SSH. To allow service personnel local access to the inverter.
Out domain/53 Tcp/udp
The inverter must be able to resolve domain names, to ensure scalability and
dynamic changes on the Internet (DNS). (required)
Out https/443 Tcp
As an HTTP client, the inverter uses SSL/TLS protocol connections to Aurora
Vision® servers for secure communication. The inverter uses this port for
all services, including data transmission, firmware upgrade, configuration
management, and remote command transmission. (required)
Out
dhcp/67,
dhcp/68
Udp
If DHCP service is not available, static network information must be assigned to the
inverter (preferred)
Out ntp/123 Udp The inverter uses this port for network time services (NTP). (preferred)
Out modbus/502 Tcp The inverter offer a Modbus TCP server connection on this port.
Out dns-sd/5353 Udp The inverter uses this protocol to resolve the local IP address.
Out http/80 Tcp As an HTTP client, the inverter uses this protocol to offer local connection.
9.1.2 Network Hosts
The inverter will connect to the following hosts. Some servers owned by FIMER, and others are customer or ISP servers. Servers listed as
owned by “Customer IT/ISP” must be configured in the inverter using either DHCP or as static network information.
Host Purpose Port Owner/Manager
platform.auroravision.net Data, configuration TCP:443 FIMER
gw1.auroravision.net and/or apt.
fatspaniel.net
Inverter firmware upgrade TCP:443 FIMER
Site dependent DHCP (optional) UDP:67, UDP:68 Customer IT/ISP
Site dependent DNS UDP:53, TCP:53 Customer IT/ISP
9.1.3 Inverter network configuration
The inverter requires a valid network configuration in order to operate. This information can either be provided by a DHCP server provided
by the customers network (the default), or the inverter can be configured with static network information. Regardless of how the inverter
is configured, the following information is required.
Configuration Purpose
IP Address
Allows the inverter to take part in the local network. This does not need to be a public IP
address. In most cases this is a private IP address.
Subnet mask Used to determine if two computers are on the same network.
Gateway
The IP address of the computer which will forward network traffic from the local network to an
external network
DNS Server The IP address(es) of the computer(s) which resolve domain names.