Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Bare Metal Restore with NetBackup 6.5.4 - PXE error - PXE-E74: bad or missing pxe menu and or prompt information

Created: 29 Jul 2009 • Updated: 11 Aug 2010 | 21 comments
EvgenyP's picture

HI!
When I try to restore Windows Server 2003 x86 with Bare Metal Restore option of NetBackup 6.5.4 on remote client (I try it on a physical and virtual machines), client says: PXE-E74: bad or missing pxe menu and/or promt information.
DHCP works perfectly; NetBackup BMR Boot server installed on different non-DHCP server.

It is error in boot image or not?

What will be suggestions?
Regards!

Comments 21 CommentsJump to latest comment

Mouse's picture

Basically this can happen if you have multiple PXE servers (like Altiris, RDP, etc..) or forgot to run couple of commands on your DHCP server.

Here is a technote with step-by-step guide how to configure this correctly on Windows: seer.entsupport.symantec.com/docs/309201.htm

EvgenyP's picture

Yes, but I have one PXE server only - BMR Boot Server.  BMR boot server configured normally.
This problem appears also when I try to restore win server 2003 x64. Errors is identical, clients and server at same version. 

EvgenyP's picture

PxeParser: startProxy=1, startBootServer=1
PxeParser: Packet received on port 67.
PxeParser: This is a proxyDHCP request packet
PxeParser: Doing an offer
PxeParser: Returning servers list
PxeParser: Returning boot server list
PxeParser: PXE_BOOT_ITEM type=0 layer=0
Found task number -1 for MAC: 00 50 56 85 46 98
PxeParser: Image file: No Cred
PxeParser:: Unable to load options DLL.
PxeParser: Socket and IP address from client: 68 PxeParser: Client's IP=0-0-0-0
PxeParser: Broadcasting the response packet to the client
PxeParser: Sending packet to client on port 68 IP=255-255-255-255
PxeParser: Sendto sent 300 bytes to 255.255.255.255.
PxeParser: startProxy=1, startBootServer=1
PxeParser: Packet received on port 67.
PxeParser: Packet not processed as it is received on 67 with ciaddr==0

EvgenyP's picture

I found in a register a line, branch of *BStrap*, which a parameter of REG_SZ *Vendor DLL* is in: C:\Program Files\Veritas\NetBackup\bin\BStrapOpts.dll But the file of it is not present. Maybe is an error related to it?
Need help!

Because if I utilize tftpd32.exe with suitable parameters (tftp folder, boot file), client loading with PXE... 

Mouse's picture

according to log you provided above your pixie client does not have IP assigned, but all BMR docs saying that you have to have DHCP setup correctly in order to use BMR

EvgenyP's picture

Okay, according to BMR docs and http://seer.entsupport.symantec.com/docs/309201.htm, we deleting options 60 and 43 on remote DHCP server. It is true?
Screenshot on client:
Screenshot 
How is it correct to influence DHCP, that a pxe-client saw from what start?

Mouse's picture

Have you created the SRT? Can you try to generate CD boot image from the SRT and load it into virtual machine, so we can check if your boot image is correct or not?

EvgenyP's picture

Yes, when I created image from the CRT and mount it into VM, boot start from CD (Loading Symantec Recovery...), then a process hung up on the "Please wait" screen. Howewer, it says that SRT works properly...Next step?

Mouse's picture

Can you please attach PXE log, I have one idea but I want to check it first

EvgenyP's picture

 PxeParserDebugLog.txt

PxeParser: Packet received on port 67.
PxeParser: startProxy=1, startBootServer=1
PxeParser: Packet received on port 67.
PxeParser: startProxy=1, startBootServer=1
PxeParser: Packet received on port 67.
PxeParser: This is a proxyDHCP request packet
PxeParser: Doing an offer
PxeParser: Returning servers list
PxeParser: Returning boot server list
PxeParser: PXE_BOOT_ITEM type=0 layer=0
Found task number -1 for MAC: 00 50 56 85 46 98
PxeParser: Image file: No Cred
PxeParser:: Unable to load options DLL.
PxeParser: Socket and IP address from client: 68 PxeParser: Client's IP=0-0-0-0
PxeParser: Broadcasting the response packet to the client
PxeParser: Sending packet to client on port 68 IP=255-255-255-255
PxeParser: Sendto sent 300 bytes to 255.255.255.255.
PxeParser: startProxy=1, startBootServer=1
PxeParser: Packet received on port 67.
PxeParser: Packet not processed as it is received on 67 with ciaddr==0

PxeServicesDebugLog.txt

About to start TFTP Server
StartTFTP: GetserviceName
StartTFTP: OpenSCManager
StartTFTP: OpenService
StartTFTP: StartService
StartTFTP: Service Started
Started TFTP Server.
regsitry: Discovery_Srvr_IP=172-16-0-78
LoadParsingDlls: 2 Parsing Dlls specified in Registry.
0: PXEParser.
1: ConfigServer.
TCP INFO DHCP Socket bound to: Port=67, IP=172-16-0-78
Socket INFO BINL Socket No, 196, bound to: Port=4011, IP=172-16-0-78
Joined Mcast IP: 0-0-0-0
Waiting for GetDomainInfo to execute
Obtaining computer name and Lan Group
Computer name = NB6-5-4
WorkGroup Name = IBSGROUP
WorkGroup Name = IBSGROUP
calling NetGetDCName
LanGroup is in a domain \\DC3
GetDomainInfo done..
Received DHCP Packet with 301 Bytes on port 67
PxeService: Packet #1 was NOT handled by any parsers
Received DHCP Packet with 329 Bytes on port 67
PxeService: Packet #2 was NOT handled by any parsers
Received DHCP Packet with 300 Bytes on port 67
PxeService: Packet #3 was NOT handled by any parsers
Received DHCP Packet with 300 Bytes on port 67
PxeService: Packet #4 was NOT handled by any parsers
Received DHCP Packet with 306 Bytes on port 67
PxeService: Packet #5 was NOT handled by any parsers
Received DHCP Packet with 339 Bytes on port 67
PxeService: Packet #6 was NOT handled by any parsers
Received DHCP Packet with 300 Bytes on port 67
PxeService: Packet #7 was NOT handled by any parsers
Received DHCP Packet with 300 Bytes on port 67
PxeService: Packet #8 was NOT handled by any parsers
Received DHCP Packet with 548 Bytes on port 67
PxeService: Packet #9 handled by Parser 0 (PXE_PACKET_SENT)
Received DHCP Packet with 548 Bytes on port 67
PxeService: Packet #10 was NOT handled by any parsers

Mouse's picture

had you done a "Prepare To Restore" for the client using the SRT in the NBU Admin Console?

Mouse's picture

can you give us an extract of vxlogview for OID 119 for the time of your tries?

EvgenyP's picture

28.07.2009 12:50:14.820 [Error] V-119-6 Server network failure
29.07.2009 09:48:02.273 [Error] V-119-6 Server network failure
29.07.2009 18:00:39.848 [Error] V-119-6 Server network failure
30.07.2009 10:10:57.596 [Error] V-119-6 Server network failure
 

Mouse's picture

According to the screenshot you are using ESX, can you check if all ports for PXE are open at the internal ESX firewall?
Look here: http://en.wikipedia.org/wiki/Preboot_Execution_Env...

EvgenyP's picture

 Yes, all ports are opened, because when I try simulate boot from PXE with tftpd32.exe (set dhcp server, set boot file, set tftp folder and disable BMR MTFTP & BMR PXE services), client booting from PXE perfectly. I in lockup. Probably, it is necessary to refuse from BMR in favour of WDS or another product. There is an idea that PXE the server does not give the list of files - any parser does not work...

Claudio Veronezi's picture

to create te prepare to restore job, remember to put the mac address in network config,

a very good documentation

http://seer.entsupport.symantec.com/docs/309201.htm

Cheers

Claudio Veronezi Mendes
IT Manager at Lb2 Consultoria
Londrina - Pr - Brazil