Home
MATRIXX Administration
Administering MATRIXX Engine
The topics in this section have information about maintaining, managing, and resolving issues with a MATRIXX Engine installation.
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.
Display IP Addresses and Roles
Follow this procedure to determine the IP addresses and roles for the servers or pods in an engine. The information also includes the high availability state of the cluster and the high availability state of any peer clusters in the installation.

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.
  - 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.
    - Display MATRIXX Engine Logical Identifiers
      Follow this procedure to display information about all logical components in a MATRIXX Engine installation.
    - Display IP Addresses and Roles
      Follow this procedure to determine the IP addresses and roles for the servers or pods in an engine. The information also includes the high availability state of the cluster and the high availability state of any peer clusters in the installation.
    - Display Transactions Per Second
      Follow this procedure to set how many transactions per second (TPS) the MATRIXX Engine servers or pods process. A TPS measure is useful to get a general idea of the health of the engine. Some print_engine_stats.py script TPS statistics are calculated for all engine servers or pods twice, the results are averaged, and the total for all servers or pods is returned. Other statistics only apply to the processing servers or pods, and those result tables are marked with an appropriate footnote.
    - Display Cluster States
      Follow this procedure to determine current state information for active and standby clusters. The information displayed includes the ID, IP address, role, and state of each server or pod in the local engine, and the state of any peer clusters.
    - Display MEF Contents
      Follow this procedure to view the contents of a _glossary/mef.html.
    - Display Pricing Compilation Information
      Pricing information includes the timestamp of the compile date, the user who compiled the file, the pricing repository location, and the pricing domain name. This information is retrieved from the pricing database with the MtxRequestPricingQueryStatus SubMan API.
  - 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

Display IP Addresses and Roles

Follow this procedure to determine the IP addresses and roles for the servers or pods in an engine. The information also includes the high availability state of the cluster and the high availability state of any peer clusters in the installation.

Procedure

Run the following command to retrieve cluster-level information for the engine:

kubectl exec -it engine_pod_name -n matrixx -- bash --login -c"print_blade_stats.py -C"

Information like the following is returned:

print_blade_stats.py -C -e 1 -c 2 -b 1
----------------------------------------------------------------
blade - 1:3:1 , version - 5081

time - Mon 2018-10-08T09:03:57
----------------------------------------------------------------


Cluster Stats
-------------
Node   Cluster        Service     Node  Mgmt      
  Id  LeaderId           Role    State  IP Address
========================================================
   1         1  checkpointing   active  127.0.0.1      

(On a standby processing blade the first time it is active)
Peer Cluster Stats
------------------
System Peer
Engine Cluster Cluster Schema    Cluster
    Id      Id   State Version     FQ Id   Cluster Up Time   Cluster Active Time
================================================================================================== 
     1       1 active    5110        0:0        2019-04-29           T23:12:57 0

(On standby processing blade which has been active)
Peer Cluster Stats
------------------
System Peer
Engine Cluster Cluster  Schema    Cluster
    Id      Id   State Version      FQ Id   Cluster Up Time     Cluster Active Time
==================================================================================================
     1       1  active    5110        0:0  2019-04-29T23:12:57    2019-04-27T07:01:12

Peer Cluster Stats
------------------
                                System     Peer
Engine  Cluster       Cluster   Schema  Cluster
    Id       Id         State  Version    FQ Id
===============================================
     1        1        active     5081      0:0


Processing Cluster Stats
------------------------
                                System     Peer
Engine  Cluster       Cluster   Schema  Cluster
    Id       Id         State  Version    FQ Id
===============================================
     1        3        active     5081      0:0