List of protocols
- Built-in protocols — updated along with the SSG software version. Installing a new version requires a DPI reboot, which causes traffic interruption.
If needed, they can be supplemented with up-to-date attributes from the VAS Cloud. This is only necessary for complex protocols, but the option is available for all. - Cloud protocols created by VAS Experts — are periodically updated from the VAS Cloud. This ensures that popular applications remain up-to-date as their behavior changes.
- Custom (user-defined) protocols — protocols created by users via the GUI using VAS Cloud tools. These have higher priority than those loaded from the VAS Cloud, and within them, IP:PORT takes precedence over IP and CIDR. It is possible to add a protocol based on IP, SNI, or AS. Guide.
| Protocol | ID | DPI version | Protocol group | Protocol type | Update | Description |
|---|---|---|---|---|---|---|
| documentum | 10002 | 12.2 | Unknown | Built-in | As needed | documentum operates on port 10002 and supports content and document management in EMC Documentum systems. |
| documentum_s | 10003 | 12.2 | Unknown | Built-in | As needed | documentum_s operates on port 10003 and provides secure communication for EMC Documentum services. |
| emcrmirccd | 10004 | 12.2 | Unknown | Built-in | As needed | emcrmirccd operates on port 10004 and is used by EMC Remote Mirror CCD for data mirroring control. |
| emcrmird | 10005 | 12.2 | Unknown | Built-in | As needed | emcrmird operates on port 10005 and supports EMC Remote Mirror Daemon for remote data replication. |
| mvs-capacity | 10007 | 12.2 | Unknown | Built-in | As needed | mvs-capacity operates on port 10007 and supports capacity planning and metrics reporting in MVS mainframe systems. |
| octopus | 10008 | 12.2 | Unknown | Built-in | As needed | octopus operates on port 10008 and is used for control and orchestration in the Octopus cloud or container management platform. |
| swdtp-sv | 10009 | 12.2 | Unknown | Built-in | As needed | swdtp-sv operates on port 10009 and supports server operations in the Secure Wireless Data Transfer Protocol. |
| rxapi | 10010 | 12.2 | Unknown | Built-in | As needed | rxapi operates on port 10010 and supports data access in RxAPI-based medical or insurance communication systems. |
| zabbix-agent | 10050 | 12.2 | Unknown | Built-in | As needed | zabbix-agent operates on port 10050 and enables metric collection from hosts for the Zabbix monitoring system. |
| zabbix-trapper | 10051 | 12.2 | Unknown | Built-in | As needed | zabbix-trapper operates on port 10051 and receives incoming data and alerts pushed to the Zabbix server. |
| qptlmd | 10055 | 12.2 | Unknown | Built-in | As needed | qptlmd operates on port 10055 and supports QPT License Manager Daemon for license management in QPT systems. |
| amanda | 10080 | 12.2 | Unknown | Built-in | As needed | Advanced Maryland Automatic Network Disk Archiver, a backup solution protocol. |
| famdc | 10081 | 12.2 | Unknown | Built-in | As needed | famdc operates on port 10081 and is used by FAMDC (File Access Management Daemon Client) for file access control. |
| itap-ddtp | 10100 | 12.2 | Unknown | Built-in | As needed | itap-ddtp operates on port 10100 and supports Device Data Transfer Protocol for ITAP infrastructure systems. |
| ezmeeting-2 | 10101 | 12.2 | Unknown | Built-in | As needed | ezmeeting-2 operates on port 10101 and supports EZMeeting 2 for extended conferencing features. |
| ezrelay | 10103 | 12.2 | Unknown | Built-in | As needed | ezrelay operates on port 10103 and is used by EZRelay for relaying data in EZMeeting systems. |
| swdtp | 10104 | 12.2 | Unknown | Built-in | As needed | swdtp operates on port 10104 and enables encrypted data transfer over wireless networks using the Secure Wireless Data Transfer Protocol. |
| bctp-server | 10107 | 12.2 | Unknown | Built-in | As needed | bctp-server operates on port 10107 and provides server-side communication in Broadcast Control Transfer Protocol environments. |
| nmea-0183 | 10110 | 12.2 | Unknown | Built-in | As needed | nmea-0183 operates on port 10110 and transports maritime GPS and navigation data using the NMEA 0183 standard. |
| nmea-onenet | 10111 | 12.2 | Unknown | Built-in | As needed | nmea-onenet operates on port 10111 and provides transport of NMEA 2000 data over IP networks in marine communication systems. |
Was this information helpful?