ACOS Architecture and Initial Access
Where ACOS runs
ACOS is the A10 Networks ADC operating system for Thunder physical appliances, vThunder virtual editions, and bare-metal deployments. It separates the control plane (CLI, GUI, aXAPI) from the data plane that forwards traffic, and it stores configuration as objects in a running-config that you save explicitly. Multi-tenancy comes from Application Delivery Partitions (aVCS): each partition has its own objects, interfaces, and administrators, so always confirm which partition context you are in.
First access
Initial access is by console or SSH to the management interface, conventionally eth0. Factory images use a management address in the 192.168.0.0/24 range and a default administrative account; current releases force a credential change at first login. The GUI is served over HTTPS from the management address. If you cannot reach it, check the management IP and mask, the default gateway, and whether the management service is enabled.
Traps
Questions often blur management and data interfaces, assume the factory address survives provisioning, or forget that an object created in one partition is invisible in another. Another trap is treating a license or feature entitlement as automatically present.
Rule of thumb
Keep management traffic on the management port or VLAN and data traffic on data ports. Before escalating, run the interface and IP show commands and state the partition you are working in. Worked example: a new appliance is unreachable at the GUI; from console you confirm the management IP and mask, find no default gateway is configured, add one, and HTTPS becomes reachable from the administrator subnet.