| Measurement |
Description |
Measurement Unit |
Interpretation |
| Status |
Indicates the current operating state of this pServer. |
|
If the pServer is booted in this LPAN, then the value of this measure will be reported as Booted. If the pServer is shutdown, then the value of this measure will be reported as Shutdown.
The numeric values that correspond to the above-mentioned measure values are as follows:
| Measure Value |
Numeric Value |
| Booted |
1 |
| Shutdown |
0 |
Note: By default, this measure reports the above-mentioned Measure Values while indicating the current operating state of this pServer. However, the graph of this measure will be represented using the corresponding numeric equivalents i.e., 0 or 1. |
| Agent_avail |
Indicates whether/not the PAN Agent is available on this pServer. |
|
A PAN Agent is an application running on the pServer that interprets PAN Manager network configuration changes to the pServer and subsequently invokes the network device configuration utility to update network interfaces on the pServer. The PAN Agent provides graceful shutdowns and basic monitoring of pServer and displays version information for the installed operating system.
This measure reports a value Yes if the PAN Agent is running on the pServer or the value No if the PAN Agent is not running.
The numeric values that correspond to the above-mentioned values are as follows:
| Measure Value |
Numeric Value |
| Yes |
1 |
| No |
0 |
Note:
By default, this measure reports the above-mentioned Measure Values while indicating whether/not the PAN Agent is running on this pServer. However, the graph of this measure will be represented using the corresponding numeric equivalents of the Measure Values as mentioned in the table above. |
| Mode |
Indicates the management mode of this pServer. |
|
PAN Manager features the ability to monitor and control a pServer through the use of a management mode setting. With managed pServers, PAN Manager automatically detects the level of monitoring it can establish with the pServer. PAN Manager offers the following managed modes for pServer administration:
- Managed — PAN Manager monitors and controls pServer health over the private management network. There are three possible levels of monitoring and status reporting:
- Enhanced — PAN Manager provides the optimal level of health monitoring for your pServers. In this level, PAN Manager uses the Heartbeat Client service to monitor pServer health. If PAN Manager does not receive a response from the pServer, and has not received any reboot or shutdown events, it initiates the restart scenario by attempting to restart on its primary pNode. (A Managed/Enhanced pServer can initiate its restart scenario approximately one minute after loss of heartbeat.) If the boot timeout interval is exceeded, the pServer fails over to its configured failover pNode.
- Basic — PAN Manager provides basic restart protection for a pServer. If PAN Manager does not receive a response from a ping to the pServer, it waits for the boot timeout interval. If the boot timeout interval is exceeded, the pServer fails over to its configured failover pNode.
Note: If you choose not to install PAN Tools on a pServer, in order for PAN Manager to provide a Managed/Basic level of support, you must configure one (or two for redundancy) pingable IP addresses on the pServer.
- Unknown — PAN Manager cannot monitor pServer health over the private management network.
- Unmanaged — PAN Manager provides no health monitoring of any kind: neither pServer failover nor pServer recovery. Placing a pServer into Unmanaged mode temporarily can be useful when a user performs:
- multiple reboots on a pServer that does not require the use of a failover pNode
- operations that can adversely affect the network connectivity of the pServer
- Unavailable - A temporary status reflecting either a Recovery or Failover is currently in-progress in the pServer.
This measure reports the above-mentioned modes to indicate the current mode of this pServer.
The numeric values that correspond to the above-mentioned modes are as follows:
| Mode |
Numeric Value |
| Unknown |
0 |
| Enhanced |
1 |
| Basic mode |
2 |
| Unavailable |
3 |
| Unmanaged |
4 |
Note:
By default, this measure reports the above-mentioned Modes while indicating the current mode of this pServer. However, the graph of this measure will be represented using the corresponding numeric equivalents i.e., 0 to 4. |
| Prim_node |
Indicates the total number of primary pNodes currently available in this pServer. |
Number |
From the pNodes previously allocated to the LPAN, the LPAN Administrator assigns a primary pNode to a pServer. The primary pNode can either be a specific pNode, or a pool of pNodes within the LPAN. If the LPAN is authorized to access a global pool, the pServer can obtain a primary pNode from the global pool if the local pool becomes depleted. |
| Fail_node |
Indicates the total number of failover pNodes currently available in this pServer. |
Number |
Failover is the act of restarting a pServer on a different pNode. (Failover requires having a PAN Server Portability license). The failover pNode can either be a specific pNode, or a pool of pNodes within the LPAN. If the LPAN is authorized to access a global pool, the pServer can obtain a failover pNode from the global pool if the local pool becomes depleted. |
| Num_vnic |
Indicates the number of virtual Network Interface Cards (vNICs) that are currently created on this pServer. |
Number |
vNIC is the Virtual Network Interface Card i.e., in this case, a PAN Manager Ethernet interface you create on a pServer. A vNIC interface functions just like a physical NIC, and is the means by which a pServer connects to an Ethernet network.
The detailed diagnosis capability of this measure lists out the names of the vNICs that are created on the pServer. |
| Num_vhba |
Indicates the number of virtual Host Bus Adapters (vHBAs) that are currently created on this pServer. |
Number |
The Virtual Host Bus Adapter (vHBA) is a PAN Manager SAN interface you create on a pServer. A vHBA interface functions like a physical HBA, and is the means by which a pServer connects to a SAN environment.
The detailed diagnosis capability of this measure lists out the names of the vHBAs that are created on the pServer. |
| Disk_block_read |
Indicates the rate at which the disk blocks are read from this pServer. |
Blocks/sec |
|
| Disk_block_write |
Indicates the rate at which the disk blocks are written to this pServer. |
Blocks/sec |
|
| Disk_read_rate |
Indicates the rate at which the disk is read from this pServer. |
Ops/sec |
A dramatic increase in this value may be indicative of an I/O bottleneck on the pServer. |
| Disk_write_rate |
Indicates the rate at which the disk is written to this pServer. |
Ops/sec |
| User_cpu |
Indicates the percent of CPU utilized in this pServer at the user level. |
Percent |
|
| Sys_cpu |
Indicates the percent of system CPU that is utilized in this pServer. |
Percent |
|
| Idle_cpu |
Indicates the percent of idle CPU in this pServer. |
Percent |
|
| CPU_util |
Indicates the percent of overall CPU utilization of this pServer. |
Percent |
A high value indicates that the pServer may consume more CPUs than normal. |
| User_nice_cpu |
Indicates the percent of overall CPU utilization of this pServer. |
Percent |
A high value indicates that the pServer may consume more CPUs than normal. |
| Total_mem |
Indicates the total memory available in this pServer. |
MB |
|
| Free_mem |
Indicates the amount of memory that is available for use in this pServer. |
MB |
|
| Used_mem |
Indicates the amount of memory that is already utilized in this pServer. |
MB |
|
| Mem_util |
Indicates the percentage of memory that is utilized in this pServer. |
MB |
Ideally, the value of this measure should be low. While sporadic spikes in memory usage could be caused by one/more rogue processes on the system, a consistent increase in this value could be a cause for some serious concern, as it indicates a gradual, but steady erosion of valuable memory resources. If this unhealthy trend is not repaired soon, it could severely hamper system performance, causing anything from a slowdown to a complete system meltdown. |
| Total_swap_mem |
Indicates the amount of memory that is available for swap in this pServer. |
MB |
|
| Free_swap_mem |
Indicates the amount of swap memory that is available for use in this pServer. |
MB |
A high value is desired for this measure, as a consistent decrease in this value is a sign of excessive swap usage, which in turn signals a memory bottleneck. |
| Used_swap_mem |
Indicates the amount of swap memory that is currently utilized by this pServer. |
MB |
Significant or consistent memory swapping indicates that the pServer is severely overcommitted and that performance degradation is imminent or actively occurring. |
| Swap_mem_util |
Indicates the percentage of swap memory that is utilized by this pServer. |
Percent |
A high value is indicative of a contention for memory resources on the pServer. |
| Pkts_rec_rate |
Indicates the rate at which the packets are received by this pServer. |
Packets/sec |
A sudden/steep increase in this value may be indicative of an I/O bottleneck on the server. |
| Pkts_send_rate |
Indicates the rate at which the packets are sent from this pServer. |
Packets/sec |
| Failure_rate |
Indicates the rate at which the packets failed in this pServer. |
Failures/sec |
|
| Pkts_rec |
Indicates the total number of packets received in this pServer. |
Packets |
A dramatic increase in this value may be indicative of an I/O bottleneck on the server. |
| Pkts_send |
Indicates the total number of packets sent from this pServer. |
Packets |
| Bytes_rec |
Indicates the amount of data received by this pServer. |
Bytes |
|
| Bytes_send |
Indicates the amount of data sent from this pServer. |
Bytes |
|
| Compres_pkts_rec |
Indicates the amount of compressed packets received in this pServer. |
Packets |
|
| Compres_pkts_send |
Indicates the amount of compressed packets sent from this pServer. |
Packets |
|
| Rec_drop |
Indicates the number of data packets that were dropped while data is being received in this pServer. |
Packets |
Ideally, the value of this measure should be zero. |
| Rec_error |
Indicates the number of error packets present in the data that was received by this pServer. |
Packets |
Ideally, the value of this measure should be zero. |
| Rec_overruns |
Indicates the number of overrun packets present in the data that was received by this pServer. |
Packets |
|
| Send_drop |
Indicates the number of data packets that were dropped while data is sent from this pServer. |
Packets |
Ideally, the value of this measure should be zero. |
| Send_error |
Indicates the number of error packets present in the data that was sent from this pServer. |
Packets |
Ideally, the value of this measure should be zero. |
| Send_overruns |
Indicates the number of overrun packets present in the data that was sent from this pServer. |
Packets |
|