Installation Checks⚓︎

The checks that confirm a fresh installation or an upgraded platform is ready for service: every workload running at the release version, the management path to xControl established and synchronized, the radio connected, monitoring receiving the site, and, after an upgrade, the existing configuration and subscribers intact.

EXP-INS-001 — Platform readiness after installation⚓︎

Objective. Every workload of a newly installed xCore is running at the release version, no container is restarting, every network function reports healthy, and the Site is registered with xControl at that version.

Preconditions

• Platform
  • The xCore is installed per the installation guide and the installer reports success.
  • You know the release version that was installed and the Kubernetes namespace of the xCore.
• Tooling and access
  • Read access to the cluster with kubectl.
  • Access to the CLI.
  • Log in to xControl with an account that can view the Mobile Asset under test.

Procedure

Pass criteria

• Every pod is ready, and no pod restarts during the fifteen minutes that follow the installer's completion.
• Every Expeto image tag and the chart version equal the release version, and third-party images match the release notes.
• Every network function reports healthy.
• The Site is online in xControl with the release's agent version.

Deployment notes

• Kubernetes-operator managed core: The core is described by a Site resource rather than a Helm release. Replace the helm list step with kubectl get site <name> -n <namespace> -o jsonpath='{.status.conditions[?(@.type=="Ready")].status}' and expect True, and check that {.status.observedGeneration} equals {.metadata.generation}. The CLI sidecar is named agent-cli, and read node lists the SMF only; check the other network functions through their pod status.

Evidence collected: Kubernetes pod and node status; CLI output; xControl screenshot.

EXP-INS-002 — Management path and subscriber synchronization⚓︎

Objective. The xCore agent holds an outbound connection to xControl, the Site reports online, and the subscriber data held by the xCore matches what xControl has provisioned for it.

Preconditions

• Mobile Asset
  • At least one Mobile Asset is provisioned on a System of the Site.
• Tooling and access
  • Log in to xControl with an account that holds the ADMIN role.
  • Access to the CLI.
  • A signalling capture on the xCore's egress interface, filtered to TCP port 443 (capture point 6).
• Procedures executed first
  • EXP-INS-001 — Platform readiness after installation

Procedure

Pass criteria

• The agent connection is outbound only.
• The Site is online within five minutes of an agent restart.
• The full synchronization check reports zero discrepancies and the record counts match.

Evidence collected: 3GPP signalling capture (pcap); CLI output; xControl screenshot.

EXP-INS-003 — Radio access node connection⚓︎

Objective. The customer's eNodeB or gNodeB establishes its control-plane association with the xCore, the xCore accepts the radio's PLMN and tracking area, and xControl shows the Private Radio as connected.

Preconditions

• Platform
  • The radio is configured with the xCore's MME or AMF address, the PLMN and the tracking area code agreed for the Site, and is powered off.
  • A Private Radio with the identifier <PLMN>-<Cell ID> of the radio exists on the Site in xControl with status Enabled.
• Tooling and access
  • Log in to xControl with an account that holds the ADMIN role.
  • A signalling capture on the xCore interface facing the radio (capture point 1).
  • Access to the CLI.
• Procedures executed first
  • EXP-INS-001 — Platform readiness after installation

Procedure

Pass criteria

• The setup exchange completes with a Response, not a Failure, and the served PLMN and tracking area are the agreed ones.
• The Private Radio shows Connected within two minutes of the radio reporting on air.

Evidence collected: 3GPP signalling capture (pcap); xControl screenshot; CLI output.
References: 3GPP TS 36.413 §8.7.3 (S1 Setup); 3GPP TS 38.413 §8.7.3 (NG Setup).

EXP-INS-004 — Monitoring path⚓︎

Objective. The new Site's metrics reach xView with the Site's labels, its scrape targets are up, and no critical alert is firing for it.

Preconditions

• Tooling and access
  • Access to the xView Prometheus query interface and Grafana.
• Procedures executed first
  • EXP-INS-001 — Platform readiness after installation

Procedure

Pass criteria

• Every scrape target of the Site is up within ten minutes of the install completing.
• The Site's series carry its Customer and Site labels.
• No critical alert is firing for the Site.

Evidence collected: xControl screenshot.

EXP-INS-005 — Upgrade and post-upgrade regression⚓︎

Objective. A platform upgrade completes with every workload at the new version, leaves the configuration and the provisioned Mobile Assets intact, restores service to connected devices without manual intervention, and passes the installation and upgrade verification set.

Preconditions

• Platform
  • The upgrade package or chart version is available and the upgrade procedure of the installation guide is at hand.
  • A maintenance window is agreed; the upgrade interrupts service.
  • The results of the installation and upgrade verification set on the current version are at hand as the baseline.
• Mobile Asset
  • One Mobile Asset is connected and passing data (execute the UE-initiated attach procedure first if it is not).
• Tooling and access
  • Read access to the cluster with kubectl.
  • Log in to xControl with an account that holds the ADMIN role.
• Procedures executed first
  • EXP-INS-001 — Platform readiness after installation
  • EXP-INS-002 — Management path and subscriber synchronization

Procedure

Pass criteria

• Every workload runs the new version and the Site reports the new agent version.
• Systems, Private Radios and Mobile Assets are unchanged.
• Connected devices regain service without manual intervention, and the measured interruption is recorded in the results sheet.
• The installation and upgrade verification set passes on the upgraded platform.

Postconditions

• Record the measured service interruption in the results sheet.

Deployment notes

• Kubernetes-operator managed core: Fields of the Site definition that require a restart are rejected by the platform's admission check unless the Site is first placed in maintenance mode; the installation guide's upgrade procedure includes that step.

Evidence collected: Kubernetes pod and node status; xControl screenshot; UE connectivity check.