Why Do I See Erroneous Data In The Server Properties When Viewed From The Deployment Server Console?
Article: 123
Applies to: All releases
Memory
One of the hardware properties reported by the Deployment Server Console is RAM. For a Linux-based target
server, the RAM information is obtained by the Deployment Agent for Linux (adlagent) by reading the MemTotal value
from the file, /proc/meminfo, on the Linux server. The MemTotal value is described as the "Total usable ram
(i.e. physical ram minus a few reserved bits and the kernel binary code)",
which means the RAM reported in the console will be something less than the total physical memory in the server.
This RAM value in the hardware properties is for reporting purposes only and is not used in the functionality
of deploying an operating system to a targer server.
If the RAM value displayed is "MB MB total" with no free memory value listed, perform a Get Inventory
on the server which will refresh this value. This issue has only been seen with Red Hat Linux on a small
number of servers after a Linux scripted install. No impact to server deployment functionality.
PXE
Another hardware property field reported is PXE. For a Linux-based target server, the PXE value is obtained by
the Deployment Agent for Linux (adlagent) reading a PXE stamp that is written to a location on the hard drive. For some
Linux distributions, GRUB is occupying the same sectors of the disk that this PXE stamp is used. In this case,
the PXE stamp will not be updated. The PXE value in the properties window in this instance will show "N/A"
even though PXE is supported. This field is for display purposes only and does not impact the functionality of the
target server being able to PXE boot at the next reboot.
|
Printable version
