Acme Packet

This guide covers Acme Packet session border controllers (now Oracle Communications SBCs) running the ACMEPACKET CLI.

Prepare a backup account

Classic Acme Packet software uses fixed local accounts — a user-level login and an admin (superuser) level — rather than freely named local users. Displaying the running configuration is a superuser-mode operation, so QUARK needs both the login password and the superuser (enable) password.

If your software release supports external authentication (RADIUS/TACACS+) or locally defined named accounts, create a dedicated netwatch-backup account there and map it to a privilege class that can enter superuser mode and display the configuration.

Enable SSH access

Enable the SSH server on the management (wancom/eth0) interface in the bootparams or management configuration, and confirm the management IP is reachable from the collector. Where your release supports management access controls on the administrative interface, restrict SSH to the collector's IP address.

Platform notes

• QUARK logs in, elevates to superuser mode with the enable password you supply, and displays the running configuration; it never issues configuration or activation commands.
• Older units may default to Telnet management. Prefer SSH; use Telnet only if the installed release lacks SSH support.

Enable backup in Netwatch

Once the device is prepared, open its host in Netwatch (Data collection > Hosts) and add the Config Backup macros — the supported status flag, the model code for this platform, and the credentials you created. See Getting started for the full macro list and values.