Service Orchestration FAQs

Anuta ATOM supports brownfield service discovery, where the standard services can be discovered and mapped back to the service catalogue that ATOM offers out-of-box. These discovered services could include L2/L3 services, IETF L2/L3 VPN services, firewall services, datacenter application delivery services, CPE onboarding services, EVPN services, and other multi-domain use cases.

Anuta ATOM supports both legacy devices that support only CLI and modern devices that support YANG over NETCONF. For legacy devices, ATOM has common YANG models to address the standardization, while it can directly ingest the schema from devices supporting YANG over NETCONF. Once the service is configured, the latest configuration is retrieved for configuration consistency. ATOM supports a variety of interfaces – NETCONF, CLI, SNMP, AMQP, SNMP TRAP, Syslog, HTTP(S) and Vendor specific APIs. ATOM Device Adapter allows Any Device interface to be modeled.

Anuta ATOM checks the resource availability before generating the commands and configuring a device. In the event of a device becoming unresponsive or going offline, ATOM will roll back the services without leaving any stray configurations on the device. This ensures that there is always a consistent network state.

Yes. Anuta ATOM supports a dry-run mode where one can verify the commands that ATOM will push to configure the devices.

This can either be addressed using Anuta ATOM’s common YANG models or using ATOM’s low code automation that can directly interact with the device to perform configurations.

Anuta ATOM offers out-of-box service models for routers, switches, load balancers, firewall & IPAM devices. Some of the common ready-to-consume services include L2/L3 services, L2/L3 VPN, ACL services, Service chaining use cases such as Datacenter Application delivery services, and many other customs services.

Any service for which the life cycle has to be maintained are ideal candidates for service orchestration. The use cases could include multiple touch points where each device may belong to a different vendor and may have different access types such as CLI, YANG over NETCONF or API. ATOM offers the abstraction layer and masks the complexity of having to learn different vendor commands. Common use cases include L2/L3 services, IETF L2/L3 VPN services, OpenConfig based L3 VPNs, firewall services, datacenter application delivery services, CPE onboarding services, EVPN services, and other multi-domain use cases.

Yes, ATOM transactions support auto rollback. Re-Try is available for operations that are past the reservation phase and encountered transient operation errors such as device connectivity issues.

ATOM supports service compliance that helps to maintain 100% service uptime. Service compliance module detects any changes to the service configurations – even if the service spans across multiple devices, and notifies and remediates to maintain SLAs.

Yes, several industry best practices are already offered as part of ATOM’s service catalogue. Customers could use them directly or customize to their requirements.

Anuta Networks offers ATOM SDK where customers with DevOps skill sets can create or extend service models.