3PAR System Reporter User’s Guide | System Reporter 2.8 |
10.3.3 The system Table
The system_3 table contains a row for each InServ system that has been sampled. A single physical InServ may have multiple entries in this table because any changes in the columns for that system will result in a new row in the table.
Table
Column | Type | Comment |
|
|
|
uniq_id | INTEGER PRIMARY | A unique identifier for the InServ system |
| KEY | instance. All samples in the data tables have |
| (AUTO_INCREMENT) | this uniq_id in the sys_uid column. |
|
|
|
serial | INTEGER NOT NULL | Serial number of the InServ. |
|
|
|
name | VARCHAR(32) NOT | InServ system name, This is what gets used in |
| NULL | most reports to identify the system. |
|
|
|
mhz | INTEGER NOT NULL | The CPU frequency in MHz. For os_rev prior |
|
| to 2.2.2, the MHz is used to calculate the |
|
| times for the service time histogram buckets. |
|
| For os_rev of 2.2.2 or later, the service time |
|
| histogram buckets are in terms of absolute |
|
| time in milliseconds rather than relative to |
|
| CPU frequency. See Service Time Histogram |
|
| |
|
|
|
ip_name | VARCHAR(32) NOT | IP Address of the system. |
| NULL |
|
|
|
|
os_rev | VARCHAR(32) NOT | InFormOS revision. This is needed in some |
| NULL | cases to determine how to interpret some |
|
| data. For example, see the mhz column |
|
| description above. |
|
|
|
system_model | VARCHAR(32) NOT | System hardware model, for example: |
| NULL | InServ S400X |
|
| InServ T400 |
|
|
|
10.4 | Administrative Tables |