The BTS Site Manager, also referred to as the local Element Manager, is the tool used to connect directly to an individual AirScale base station to view its local configuration, hardware inventory, logs, and run element- level diagnostics. It is typically used when an engineer needs granular, site-specific information that may not be fully visible through the centralized system, or when NetAct connectivity to the site is impaired. NetAct CM Editor is used for network-wide configuration management of many sites from the central OSS, NetAct PM Reports aggregates performance counters across the network, and the SON Network Optimizer automates parameter tuning across multiple cells. Because the question specifically asks about direct, single-element access for local diagnostics rather than network-wide operations, the BTS Site Manager is the correct answer, complementing NetAct in a complete remote operations toolkit.

A full site backup typically captures both the currently running software load (or a reference to it) and the complete configuration data for the network element, providing the most comprehensive restore point - useful before major changes such as software upgrades or significant hardware-related maintenance. A partial, or configuration-only, backup captures just the configuration data - the set of parameters defining how the element is provisioned - without necessarily including the software image itself. Configuration-only backups are commonly used before smaller-scope parameter changes, where the software load itself is not expected to change, since they are typically faster to perform and require less storage. Choosing the appropriate backup type depends on the scope of the planned change: a software upgrade warrants a full backup, while a routine parameter adjustment may only require a configuration backup. Neither backup type is restricted to alarm history or performance counters, and both can typically be performed remotely without requiring a field engineer to be present.

When basic transport/IP connectivity to a site is confirmed as up but an O and M management session still cannot be established, the issue is likely at a higher layer than physical or network-layer reachability.
Common causes include expired or mismatched security certificates, incorrect login credentials, or a misconfigured O and M IP address or management VLAN on the base station itself. A layered troubleshooting approach moves from transport, to network, to application/management-layer checks once lower layers are confirmed functional. Replacing the RF module addresses a hardware radio issue, not an O and M session
/authentication problem, and would be premature without further evidence. Adjusting reference signal power is unrelated to management connectivity. Restarting the entire NetAct server is a drastic action affecting the whole managed network and is never an appropriate first response to a single-site connectivity issue.

For security, isolation, and quality-of-service reasons, AirScale base stations typically separate Operations and Maintenance (O and M) traffic from user-plane traffic (such as NG-U/N3 in 5G or S1-U in 4G) using distinct VLANs and/or IP addressing on the transport network. This separation ensures that configuration commands, alarm reporting, and software transfers travel on a logically isolated path from subscriber data, reducing the risk that issues or attacks affecting the user-plane path could impact management connectivity, and allowing each traffic type to be independently prioritized and monitored. It is incorrect that they must share identical addressing, that O and M cannot use IP (modern AirScale O and M is IP-based and typically carried over the same physical transport with logical separation), or that user-plane traffic configuration is unrelated to transport - transport interface parameters configured via NetAct CM directly determine how user-plane traffic is carried.

Centralized Operations Centers connect to many geographically distributed 5G sites over shared transport infrastructure that may include third-party or public network segments. A secure tunnel, typically using IPsec, is established between the Operations Center's management domain and the site's security gateway to encrypt and authenticate all Operations, Administration, and Maintenance (O and M) traffic - including configuration commands, alarm and performance data, and software transfers - protecting it from interception, tampering, or unauthorized access. This secure channel has no effect on RF transmit power, which is governed by separate cell configuration parameters, and it does not perform software compression, which is a function of the software packaging process itself. It also does not replace alarm monitoring, which is handled by NetAct's Fault Management module; rather, the VPN ensures that alarm data itself reaches the Operations Center securely.