List of protocols [Документация VAS Experts]

List of protocols

  1. 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.
  2. 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.
  3. 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.
ProtocolIDDPI versionProtocol groupProtocol typeUpdateDescription
netiq-endpoint1011312.2UnknownBuilt-inAs needednetiq-endpoint operates on port 10113 and supports endpoint status reporting and diagnostics in NetIQ infrastructure.
netiq-qcheck1011412.2UnknownBuilt-inAs needednetiq-qcheck operates on port 10114 and provides quality assurance and traffic verification in NetIQ tools.
netiq-endpt1011512.2UnknownBuilt-inAs needednetiq-endpt operates on port 10115 and enables endpoint health and performance monitoring in NetIQ systems.
netiq-voipa1011612.2UnknownBuilt-inAs needednetiq-voipa operates on port 10116 and supports VoIP traffic monitoring in NetIQ performance management systems.
iqrm1011712.2UnknownBuilt-inAs needediqrm operates on port 10117 and is used for data management in IQRM (Intelligent Quality Risk Management) platforms.
bmc-perf-sd1012812.2UnknownBuilt-inAs neededBMC Performance Service Daemon responsible for reporting to management consoles.
bmc-gms1012912.2UnknownBuilt-inAs neededBMC Global Monitoring System protocol for centralized IT infrastructure monitoring.
trisoap1020012.2UnknownBuilt-inAs neededtrisoap operates on port 10200 and facilitates SOAP-based messaging in TriSoft or custom middleware frameworks.
rscs1020112.2UnknownBuilt-inAs neededrscs operates on port 10201 and supports secure messaging and communication in RSCS (Remote Systems Control Services) or enterprise integration platforms.
rsms1020112.2UnknownBuilt-inAs neededrsms and rscs operate on port 10201 and provide secure communication in RSMS enterprise messaging platforms.
apollo-relay1025212.2UnknownBuilt-inAs neededapollo-relay operates on port 10252 and is used for message relaying in Apollo communication middleware or integration platforms.
axis-wimp-port1026012.2UnknownBuilt-inAs neededaxis-wimp-port operates on port 10260 and supports remote management of Axis network devices via the WIMP protocol.
blocks1028812.2UnknownBuilt-inAs neededBlocks protocol related to modular data streaming or interactive software platforms.
cosir1032112.2UnknownBuilt-inAs neededcosir operates on port 10321 and supports COSIR (Centralized Operations System Interface Repository) for system interfacing.
hip-nat-t1050012.2UnknownBuilt-inAs neededhip-nat-t operates on port 10500 and enables NAT traversal for the Host Identity Protocol (HIP) using UDP encapsulation.
MOS-lower1054012.2UnknownBuilt-inAs neededmos-lower operates on port 10540 and facilitates lower-level control messaging in MOS protocol integrations.
MOS-upper1054112.2UnknownBuilt-inAs neededmos-upper operates on port 10541 and supports upper-level messaging in MOS newsroom integration systems.
MOS-aux1054212.2UnknownBuilt-inAs neededmos-aux operates on port 10542 and supports auxiliary services such as metadata or thumbnail transfers in MOS systems.
MOS-soap1054312.2UnknownBuilt-inAs neededmos-soap operates on port 10543 and enables standard SOAP messaging for Media Object Server (MOS) environments.
MOS-soap-opt1054412.2UnknownBuilt-inAs neededmos-soap-opt operates on port 10544 and provides optimized SOAP communication for MOS protocol applications.

Was this information helpful?