Forum Discussion

Lacey_Chu's avatar
Lacey_Chu
Level 4
9 years ago

BMR restore linux client failed with error "no boot file received"

Hi Expert,

My NBU master server, media server and boot server is on the same linux machine. The client is also linux server.

Both are using NBU 7.7.

I configured dhcp on boot server.

After preparing to restore, I started the BMR network boot, but I saw that there was an error "no boot file received" then network boot failed.

Could anyone help me on this issue?

Regards,

Lacey

 

  • The client and the boot server need to be on the same subnet.

    You will neet to provide another Linux boot server that is on the same subnet as the client.
    All explained in NBU for BMR manual.

    Extract:

    Linux boot server:
    Each network segment that has Linux clients must have a Linux boot server.
    Though in case of VLAN (Virtual Local Area Network) setup case, you can configure your switch
    settings to route network boot requests packets to server located at other VLAN than where client
    exists. This way a single Linux boot server can recover Linux clients belonging to different VLANs.

10 Replies

  • actually, I remembered it was "no boot filename received" error.

  • Master/Media/BMR server:  O/S name, and OS version, and OS patch level?

    Master/Media/BMR server  Please confirm whether NetBackup is base v.7.7, or whether it is v7.7.1 or v7.7.2?

    Recovering BMR client:  O/S name, and OS version, and OS patch level?

    Recovering BMR client:  NetBackup version and patch level?

     

  • Master/Media/BMR server:  O/S name, and OS version, and OS patch level?

    -----redhatlinux6.7

     

    Master/Media/BMR server  Please confirm whether NetBackup is base v.7.7, or whether it is v7.7.1 or v7.7.2?

    ------base v7.7

     

    Recovering BMR client:  O/S name, and OS version, and OS patch level?

    -----redhatlinux6.7

     

    Recovering BMR client:  NetBackup version and patch level?

    ------base v7.7

  • The following ports all need to be open on a NetBackup Server when it is performing all three roles of:  master, media, bmr-boot:

    udp/67

    udp/69

    tcp/445

    tcp/4011

    tcp/1556

    tcp/13724

    .

    And for the BMR network booting client, the Ports Reference Guide says that only:

    tcp/1556        is required

    ...but I have found that:

    tcp/13724      is also required

    ...i.e. although the BMR booting client will not be running a firewall, your network might be... so both of these ports need to be open across network firewalls too.

  • Is the client in a different VLAN or subnet - i.e. is the client routed via a different gateway?

    If yes, then you may need to ask your network switch admins to enable the 'PXE Helper' service/setting on the gateways in their LAN switches.

  • Does your master/media/bmr-boot server have a firewall running?

    iptables -L
  • [root@qin ~]# iptables -L
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination         

    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination         

    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination         
    [root@qin ~]#

  • yes, the client routed via a different gateway.

    do you have detailed procedure about how to enable the 'PXE Helper' service/setting on the gateways in their LAN switches.

    greate thanks to you.

  • Apologies, I do not have any procedures for setting 'PXE Helper'.   AFAIK, it is a LAN switch/router configuration setting.  I think you need to talk with your LAN switch engineers.

  • The client and the boot server need to be on the same subnet.

    You will neet to provide another Linux boot server that is on the same subnet as the client.
    All explained in NBU for BMR manual.

    Extract:

    Linux boot server:
    Each network segment that has Linux clients must have a Linux boot server.
    Though in case of VLAN (Virtual Local Area Network) setup case, you can configure your switch
    settings to route network boot requests packets to server located at other VLAN than where client
    exists. This way a single Linux boot server can recover Linux clients belonging to different VLANs.