If PXE is not working where should I start troubleshooting?
Can you help me understand the PXE booting process better?
Deployment Solution 8.x
The content of this KB is specifically to troubleshoot the PXE boot process was implemented in DS 8.x. We will not troubleshoot specific PXE Error codes in this KB - those are industry standard and well documented elsewhere.
The options (response XML) returned from the SMP include Boot, Client, Image, Architecture, and if there's a Job running or not. It looks a little like this:
<response boot="0" client="1" image="LinuxInstall" arch=”1” jobrunning="1" />
The possible values of each of these are:
0 – Pxe Boot
1 – Automation Boot
2 – Production Boot
0 – Managed
1 – Predefined
2 – Unknown
Image attribute should have image name
1 – x86
2 – x64
Jobrunning attribute (If there is a job scheduled for this client or not)
0 – Not running
1 – Running
Be aware of the process.
If you're getting M0F, that's not an error - that's the PXE server telling the client to go to production. Why it's being told to go to production may be an error, but the response is not, and it indicates that PXE is listening and responding. Once you know the process, you'll know where something may not be working as expected and be able to more quickly find an answer.
Know the logs.
The PXE log, which is off by default, is called SBSLog_PXE will show you most of the activity of the PXE Server service. A log level of 5 which shows you most of what you need to know and may save space. Complete logging is at either 15 or 255 which are essentially the same. This log file is in the same location as the server Service, which is, by default, under "Altiris Agent\Agents\Deployment\Task Handler\SBS," if installed.
You'll see lines like the following:
The 4th bullet above shows the request from a client, which again, looks like this:
Tue Dec 31 11:20:15 - 1704 SbsPxeInterface.cpp Sbs::SbsPxeInterface::ListenDone 168 Debug Req: IP=<CLIENT IP ADDRESS>, MAC=<CLIENT MAC ADDRESS>, UUID=4C4C4544-0044-4A10-8051-C4C04F315231, SerNum=DDJQ1R1
This is the data sent back to the NS, which is used in a Query that can be seen in a Profile trace.
The ASPX will then return the data to the PXE server, and in the PXE logs, you should see an entry like the following:
Tue Jan 07 12:58:40 - 5840 SbsHttpClient.cpp Sbs::SbsHttpClient::OperationDone 136 Debug NSResp: bytes read 314, 'HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Date: Tue, 07 Jan 2014 18:58:40 GMT
<response boot="0" client="0" image="a" arch="" jobrunning="1" />'
Known Issues in communication:
We have seen a few issues in the PXE Server log that are worth mentioning if you see them.
The 5th bullet in the list of possible entries (above under "know the logs") shows "NS Response parse failure". This indicates that data returning from the NS after a request is bad. We have seen at least two types of bad data returned, including:
Pay Attention to Configuration.
Know how to configure the PXE options in the console under Settings | Deployment | NBS General Settings. Also be aware that, for these settings to actually be working, they must be reflected in the SBConfiguration.XML file on the Site Server. That is the file that the PXE Server Service is actually paying attention to, and is located in the same directory.
Some key notes: