NetAct is Nokia's centralized Operations Support System (OSS) and is the primary platform used by NOC and technical support teams to manage AirScale 5G base stations from a centralized Operations Center. It integrates Fault Management (FM), Configuration Management (CM), Performance Management (PM), and Software Management (SWM) modules into a single environment, allowing engineers to monitor alarms, push configuration changes, review KPI dashboards, and manage software lifecycle activities across the entire RAN estate without visiting individual sites. While element-level tools such as BTS Site Manager exist for local diagnostics on a single base station, NetAct is the day-to-day platform for remote, network-wide operations. NetGuard focuses on security analytics, CloudBand on NFV infrastructure orchestration, and Nokia Digital Automation Cloud targets private wireless deployments, so none of these serve as the primary RAN operations management system referenced in remote operations procedures.

A jump server (also called a bastion host) is an intermediate, hardened system that NOC personnel must authenticate to before establishing management sessions, such as SSH or NetAct client connections, to production base stations. This design reduces the attack surface of the network because production elements only need to accept management connections originating from a small number of tightly controlled, monitored hosts, rather than from every individual engineer's workstation across potentially varied locations and security postures. Jump servers also provide a natural point for enforcing multi-factor authentication, centralized session logging, and periodic access reviews. An edge router forwards traffic between networks but is not an access-control checkpoint for engineer sessions. A load balancer distributes traffic across multiple servers for performance/availability, and a DNS server resolves hostnames to IP addresses - neither performs the security gatekeeping function described.

Cell reselection priority parameters are broadcast to idle-mode UEs and inform them how to prioritize different frequency layers (such as a 5G band versus an LTE band, or multiple 5G bands) when more than one suitable cell is available for camping. By assigning higher reselection priority to certain layers, an operator can influence idle-mode UE distribution - for example, encouraging UEs to camp on a 5G layer where available to ensure faster initial access to 5G services, or directing UEs away from a layer that is being prepared for maintenance. These parameters work alongside reselection thresholds and timers that prevent excessive reselection (ping-ponging) between layers. They do not control network registration eligibility (which depends on subscription and PLMN matching), transmit power limits (a separate RF parameter), or encryption key management (a security function handled through different mechanisms), but they play an important role in idle-mode load distribution and user experience from the moment a device wakes up.

NetAct supports configuring automatic notifications, such as email or SMS alerts, to be sent to designated NOC personnel when alarms of a certain severity - commonly Critical - are raised. This ensures severe issues are brought to the attention of responsible engineers promptly, even if no one is actively viewing the live FM dashboard at that exact moment, helping reduce the time between a fault occurring and corrective action beginning. This notification mechanism complements, rather than replaces, the FM dashboard, which remains necessary for detailed investigation, alarm correlation across the network, and ongoing monitoring of all severity levels. It does not automatically fix any underlying fault - it is purely an awareness mechanism - and has no effect on how many alarms the network actually generates, which is determined by real fault conditions and configured alarm definitions/thresholds, not by notification settings.

A NetAct configuration (network) audit tool compares the parameter values currently deployed on live network elements against a defined reference or baseline configuration - sometimes called a golden configuration or template - and reports any deviations or inconsistencies found. This is highly valuable for remote operations because it can detect unauthorized or accidental configuration changes, configuration drift following maintenance activities, or sites that failed to receive an intended bulk update correctly, all without requiring a physical site visit. It directly supports standard provisioning workflows by allowing engineers to confirm that planned configuration changes were applied correctly and consistently across all targeted base stations. The tool does not perform physical inspection of cabinets (a field activity), does not measure power consumption (handled by environmental/equipment monitoring functions), and is not used to produce marketing material - its scope is strictly configuration verification within the OAM domain.