System Model Information and Capability
This page is not about testing anything. This is more of information purpose. The purpose of this tutorial is to show you how you can figure out the model of your system and how to find more detailed information/capabilities of the model.
Common examples for this case are
- Trying to multi cell test with Callbox Mini which support only one cell
- Trying to achieve the maximum throughput that is not supported by the model
- Trying to configure MIMO which are not supported by the model
Table of Contents
- System Model Information and Capability
Introduction
Understanding the hardware and software model of your system is a foundational aspect of effective system management and troubleshooting. In complex testing or deployment environments, such as those involving telecommunications equipment or specialized network devices, each model may come with unique capabilities, limitations, and supported features. Model-specific attributes like supported cellular bands, maximum throughput, and advanced functionalities such as MIMO (Multiple Input Multiple Output) can significantly affect system behavior and user expectations. Identifying your system’s model and its detailed specifications allows for informed configuration, prevents misinterpretation of error messages, and helps distinguish between configuration issues and inherent model limitations. This knowledge is especially vital when diagnosing problems, optimizing performance, or planning upgrades, as different models—even within the same product family—can have varying hardware resources, firmware support, and feature sets. By proactively verifying your system model and its capabilities, you can streamline troubleshooting processes, avoid common pitfalls, and ensure that your testing or operational objectives align with what the hardware can actually deliver. This tutorial provides a detailed, step-by-step approach to identifying your system’s model and comprehensively reviewing its supported features, empowering you to make technical decisions with confidence and clarity.
-
Context of the Tutorial
- This tutorial focuses on the process of identifying the specific model of your system or device, such as network testers or communication equipment.
- It provides methodologies for obtaining detailed model information, including technical specifications and feature sets directly from the device or its documentation.
- The approach is relevant to environments where equipment limitations may impact test outcomes and troubleshooting efforts.
-
Relevance and Importance
- Knowing your system’s model helps avoid wasted effort troubleshooting issues caused by hardware or firmware limitations, rather than configuration errors.
- It is critical for interpreting error messages accurately and understanding the root cause of operational anomalies.
- Common scenario examples include:
- Attempting multi-cell testing on devices like Callbox Mini, which only support a single cell.
- Trying to achieve throughput levels not supported by your hardware model.
- Configuring advanced features such as MIMO on models that do not support them.
-
Learning Outcomes
- Gain the ability to accurately identify your system’s model and version information.
- Learn how to retrieve detailed capability lists for your specific hardware or software revision.
- Develop the skill to distinguish between issues caused by configuration errors and those due to model limitations.
- Enhance your troubleshooting process by integrating model verification as a standard diagnostic step.
-
Prerequisite Knowledge
- Basic familiarity with your system’s user interface (CLI, GUI, or web interface).
- General understanding of your environment’s hardware or software architecture.
- Ability to access device documentation, technical datasheets, or manufacturer support resources.
- No advanced programming or engineering background is required, but attention to technical detail is recommended.
Summary of the Tutorial
This tutorial outlines procedures to determine the model name and capabilities of a system using various methods. The focus is on identifying the system’s model name through different command-line techniques, log file examination, and then referencing capability information based on the discovered model and license type.
-
Model Name Identification Procedures:
-
Using Command Prompt:
- Access the system’s command prompt.
- Observe the prompt, which displays the model name acronym (e.g., CBC-2023010100).
-
Checking the Hostname File:
- Run cat /etc/.amarisoft-product/hostname to display the contents of the hostname file.
- The output provides the system’s model identifier (e.g., CBC-2023010100).
-
Examining the LTE Log File:
- Open the LTE log file using nano /tmp/lte.log.
- Search for entries containing model information (e.g., model:Callbox Classic[20230101-00]).
- Additional hardware and OS details can be found in the log.
-
Using Command Prompt:
-
Model Capability Reference:
- After identifying the model name, consult the provided table to match the hostname acronym to the full product name and obtain detailed product information.
- Use linked resources for comparative analysis of capabilities across different AMARI Callbox Series models.
-
Determining License Capability:
- Recognize that system capability depends on both model and license type.
- Refer to the specified document to review the capabilities associated with each license type.
The procedures ensure accurate identification of the system model and an understanding of its supported features based on both hardware and licensing constraints.
Finding Model Name
There are multiple different ways to figure out model name
Command Prompt
The easiest way to figure it out is to check the command prompt. The command prompt shows the acronyms for the model name as shown below.
|
[root@ |
Hostname file
Check out the contents of hostname file by running 'cat /etc/.amarisoft-product/hostname' and you will get the result like this
|
[root@CBC-2023010100 ~]# cat /etc/.amarisoft-product/hostname |
lte log
You can find more detailed information from lte.log. run 'nano /tmp/lte.log and find the information as shown below.
|
2024-08-31 18:02:27 [OTS] - OTS: Start service v2024-08-09 host: user: root model: cpu: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz mem: 16G motherboard: ASUSTeK COMPUTER INC. PRIME Z590M-PLUS os: fedora v34 boot: BOOT_IMAGE=(hd0,gpt3)/vmlinuz-5.17.12-100.fc34.x86_64 root=/dev/mapper/fedora_localhost--live-root ro res> target: linux 2024-08-31 18:02:27 [OTS] - OTS: Set hyperthreading off |
Finding Model Capability
Once you find the model name (mostly Acronym) as shown above, you can find the capability of each model from following table
|
Product Name |
Hostname |
Product Information |
|
Callbox Extreme |
|
|
|
Callbox Ultimate |
|
|
|
Callbox Advanced |
|
|
|
Callbox Classic |
|
|
|
Callbox Mini |
|
|
|
UE Simbox MBS |
|
|
|
UE Simbox E |
|
|
|
UE Simbox |
|
- AMARI Callbox Series comparison
- Select an AMARI Callbox based on target configuration
Finding LicenseCapability
The capability of a system is capped not only by the model but also by License type as well. For the capability of each license type, refer to this document.