Actelis Networks ML700 - NE Management Communication Protocols and Ports

Management Configuration NE Management Communication Protocoles and Ports
3-2 User Manual ML700
NE Management Communication
Protocoles and Ports
Each ML NE can be managed via different communication protocols:
 Prompted TL1 via TCP port 3083 (not configurable) - for man-machine interface
 Unprompted TL1 via TCP port 3082 (not configurable) - for machine-machine interface
 Prompted CLI via TCP port 23 (telnet attached) – for man-machine interface
 Discovery Protocol via UDP port 3087 (not configurable) - for ML discovery by
MetaASSIST View
 Telnet via TCP port 23 (not configurable) – to provide TL1/CLI connections described
above
 SSHv2 via TCP port 22 (not configurable) - for secure TL1/CLI connections described
above
 HTTP via TCP port 80 (not configurable) - for file transfer operations
 SNMP via UDP input port 161 (not configurable) and output port 162 (configurable)
 SNTP via UDP port 123 (not configurable) - for date and time auto-synchronization in
the LAN
 Radius Client on ML via UDP port 1812 (not configurable) – for auto-authentication by
external Radius Server
 Syslog Client on ML via UDP port 514 (not configurable) – for auto-upload of log
records to external Syslog Server
Access via each communication protocol can be controlled via Access Control List, see
Managing User Accounts (on page 12-3).
In addition, User Account (on page 12-3) and SSH features (on page 12-25) secure TL1
communication protocol
ML Link Visibility via MAV
MAV session connected to an ML NE (CO or CPE) via a CRAFT port, shows indirectly
connected CPE or CO NEs (Linked via HSL) only if the following conditions are true:
 CO and CPE are connected by copper pairs.
 The peer NE (either CO or CPE) has “Access from Peer” Enabled (factory setup) –
controls IP-less access (via craft port).
Note: A MAV Craft port session shows CO NE linked via HSL only in P2P topology of
ML700 and ML600 models (except for ML688).