At the appliance level, the integration options include:

• **SNMPv2/v3: **SNMP is primarily used for SNMP traps, but basic MIBs are also provided for GET operations, such as the interface MIB. No SNMP SET functionality is offered.

• **CLI:** the local CLI provides a non-GUI-based craft interface that could also be used as an API.

• **IPFIX:** IPFIX provides real-time telemetry flow performance data as well as firewall logging. SIEMs or OSS/BSSs that are interested in consuming performance analytics data can utilize IPFIX at the appliance level.

• **Syslog:** the appliance Syslog logs alarms, audit log events, and other local events. Each appliance supports up to 2 Syslog receivers.

• **REST API (native-mode): ** the appliance also offers a direct REST API for monitoring and configuration, but if customers have a need to access appliance-level functionality via REST, it is highly recommended to utilize the pass-through REST API accessible via Orchestrator. This prevents the need to manage individual sessions and user IDs to every appliance, as Orchestrator’s REST API can provide a single-stop point of integration.

• **Cloudinit:** the virtual EdgeConnect (EC-V) generally requires some initialization before it is discovered by the appropriate Orchestrator since EC-V is self-instantiated by the customer and is not pre-provisioned to a specific customer account, as is the case with hardware-based EdgeConnect appliances. To assist in this bootstrapping process, EdgeConnect supports a CloudInit feature, which is realized as a YAML file that contains CLI command. Upon initial boot, EC-V looks for a YAML file in a pre-specified sequence of locations and if present, will execute the CLI commands within the YAML file.

The appliance integration points utilize the following ports for access: