Home
MATRIXX Administration
Administering MATRIXX Engine
The topics in this section have information about maintaining, managing, and resolving issues with a MATRIXX Engine installation.
Checking the Statuses of MATRIXX Engine Services and Shared Storage
Follow the procedures in this section to check whether MATRIXX Engine services are running and to check the configuration and state of the shared storage.
Check the Shared Storage
Run the check_engine_start_prereqs.py script to check the contents of the mounted file system and the configuration of the mount point.

Welcome
MATRIXX Release Notes
MATRIXX Architecture
MATRIXX Installation and Upgrade
MATRIXX Configuration
MATRIXX Security
MATRIXX Integration
MATRIXX Diameter Integration
MATRIXX Call Control Framework Integration
MATRIXX TM Forum Integration
MATRIXX 5G Integration
MATRIXX 5G Event Streaming
MATRIXX Event Streaming
MATRIXX Administration
- About MATRIXX Administration
  MATRIXX Administration describes how to monitor MATRIXX Engine components and to perform daily operations for maintaining a geographically redundant system. This includes administration for the engine, Traffic Routing Agent, MATRIXX gateways and web apps, and Notification Framework. It also provides information about recovering from a total system failure.
- Administering MATRIXX Engine
  The topics in this section have information about maintaining, managing, and resolving issues with a MATRIXX Engine installation.
  - Checking the Statuses of MATRIXX Engine Services and Shared Storage
    Follow the procedures in this section to check whether MATRIXX Engine services are running and to check the configuration and state of the shared storage.
    - Check the Status of MATRIXX Engine Services
      The check_blade.py script checks that all MATRIXX services are running locally.
    - Check the Status of a Cluster
      Use the check_cluster.py script to see if all processes in a cluster are running. Use the print_blade_stats.py script to check the state of all processes and return the related IP address.
    - Check the Status of an Engine
      The check engine script checks the status of an engine.
    - Check the Shared Storage
      Run the check_engine_start_prereqs.py script to check the contents of the mounted file system and the configuration of the mount point.
  - Displaying Information About MATRIXX Engine Components
    Follow the procedures in this section to display information about MATRIXX Engine components, such as pod or server and engine IDs, software version numbers, _glossary/mef.html contents, pricing configuration information, and MATRIXX Engine version information. For information about displaying MATRIXX Engine statistics, see MATRIXX Monitoring and Logging.
  - Managing Checkpoints and Transaction Logs
    Follow the procedures in this section to change the default checkpointing behavior, create a checkpoint manually, and delete old transaction logs and transaction log files.
  - Throttle the Incoming Event Rate
    Perform the tasks in this section if you did not set the incoming event rate as part of your base configuration process.
- Administering MATRIXX Traffic Routing Agent
  The topics in this section describe administering Traffic Routing Agent (TRA) servers, including starting and stopping Traffic Routing Agent nodes and clusters. The information in this section applies to all Traffic Routing Agent functions unless otherwise noted.
- Administering the Route Cache
  The topics in this section describe administering the Route Cache.
- Administering US Tax Data
  US tax data is imported from CCH tax data, compiled in My MATRIXX, and output as compact MATRIXX Data Container (MDC) files, including an MDC file containing tax database metadata and status information. MDC files are packaged into a .zip file and loaded into the MATRIXX tax database.
- Troubleshooting Issues
  This section has information to help identify and resolve system issues.
- Appendixes
MATRIXX Web App Administration
MATRIXX Monitoring and Logging
MATRIXX Policy
MATRIXX Kafka CDR Consumer
MATRIXX Pricing and Rating
MATRIXX Pay Now
MATRIXX Subscriber Management
MATRIXX Subscriber Management API
MATRIXX Business API SDK
My MATRIXX Help
MATRIXX Backoffice Customer Tool Help
MATRIXX Third-Party Licenses
Glossary

Check the Shared Storage

Run the check_engine_start_prereqs.py script to check the contents of the mounted file system and the configuration of the mount point.

About this task

This script is called by MATRIXX Engine start-up scripts. Running the script manually beforehand is optional when you are start after a typical shutdown operation. The script does not check /etc/fstab or /etc/sudoers files, so they must be configured correctly in advance.

Perform this task on the publishing server or pod.

Procedure

Run the check_engine_start_prereqs.py script without any options on all servers or pods in the engine. Replace E1 with the ID of the active engine.
kubectl exec -it engine_pod_name -n matrixx -- bash --login -c"check_engine_start_prereqs.py E1"
Run the check_engine_start_prereqs.py script to run fsck on the shared file systems and check that the content is consistent with MATRIXX requirements:
kubectl exec -it engine_pod_name -n matrixx -- bash --login -c"check_engine_start_prereqs.py --active-cluster --check-file-system --check-contents"
The --check-file-system option must be used before each start of an engine. Without the --check-file-system option, the script only checks that all required partitions can be mounted.
Run the check_engine_start_prereqs.py script without any options to check the status for all processes in the cluster:
kubectl exec -it engine_pod_name -n matrixx -- bash --login -c "check_engine_start_prereqs.py"
Run the check_engine_start_prereqs.py script with the following options. This runs fsck on the shared file systems:
kubectl exec -it engine_pod_name -n matrixx -- bash --login -c"check_engine_start_prereqs.py --standby-cluster --check-file-system"
Note: If a shared file system is not mounted, the script tries to mount the shared storage as read-only for processing servers or pods and as read-write for publishing servers or pods. If the shared storage mount fails, the script fails and the engine does not start.