Compatible lines¶

The SACM auto-connection function (Pull) automatically identifies the line type during service adaptor boot to connect to the internet. A list of compatible lines is as follows.

Compatible connection methods	Description
PPPoE	Limited to NTT Flet’s lines, etc. See below for details
DHCP	Format not specified for if the environment allows DHCP address allocation. Available under NAT environment.
mobile PPP	Compatible only with IIJ mobile lines
RA (IPv6 Router Advertisement)	Format not specified for if the environment allows RA address allocation
static	For environments where static IP addresss setting is necessary to execute Pull. Prior to the SMF Pull operation, network configuration must be done in advance via suitable methods.

Refer to “ Country/region-based information “ for details on compatible lines.

Service adaptor communications requirements¶

The communication between service adaptors and servers on the following network segments must be available to enable SACM mangament.

Communication from service adaptors to servers¶

Network segment	Port No./Protocol
202.221.49.0/24 202.221.50.0/24 202.221.51.0/24	80/TCP 443/TCP 10010/UDP
2001:240:bb88::/48	80/TCP 443/TCP 10010/UDP

Communication from servers to service adaptors.¶

Network segment	Port No./Protocol
202.221.49.0/24 202.221.50.0/24 202.221.51.0/24	22/TCP 443/TCP
2001:240:bb88::/48	22/TCP 443/TCP

Ensure that the above communication is permitted by the service adaptor and devices like a firewall.

SACM management will not work properly if these ports are filtered. Similarly, SACM management will not work if these ports are blocked by the service adaptor’s own filter function.

If you need information for more specific filter settings, see the following individual addresses and port numbers.

Depending on the service adaptor type, there are instances where permissions are forced regardless of the configuration created by the user. This is done to ensure communications.

Communications under NAT¶

If the service adaptor is a router or other device that directly terminates PPPoE, then communication is conducted directly with LS or RS servers. For other devices, in many cases the connection to server is routed through the IPv4 NAT. The SMFv2 is compatible with communication routed through NAT and is able to conduct monitoring and Push operations.

However, note that ports like those noted above that are used for communication with the server require permissions for both the service adapter and the NAT device. In particular, because Heartbeat utilizes UDP, NAT device may require special settings.

If you need information for more specific filter settings of the NAT device, see the following individual addresses and port numbers.

Communication from service adaptors to servers (details)¶

Destination	Recipient address	Port No./Protocol	Description
SA -> LS	202.221.49.106	443/TCP	Pull purpose of use
	202.221.51.6
	2001:240:bb88::2
	2001:240:bb88::6
SA -> RS	202.221.50.101	443/TCP	Pull purpose of use
	202.221.50.105
	2001:240:bb88::0136
	2001:240:bb88::0139
SA -> Module	202.221.50.108	80/TCP	Module update
SA -> Module	2001:240:bb88::013b	80/TCP	Module update
SA -> Heartbeat	202.221.50.100	10010/UDP	Heartbeat transmission
	202.221.50.104
	2001:240:bb88::0135
	2001:240:bb88::0138
SA -> Floatlink	202.221.50.136	443/TCP	Floatlink information transmission (SA-W1 only)
SA -> Floatlink	2001:240:bb88::0165	443/TCP	Floatlink information transmission (SA-W1 only)

Communication from servers to service adaptors (details)¶

Destination	Sender address	Port No./Protocol	Description
RS -> SA	202.221.50.101	443/TCP	All Push from SACM
	202.221.50.105
	2001:240:bb88::0136
	2001:240:bb88::0139
RS -> SA	202.221.49.8	22/TCP	Used for operator-based support

SACM service manual