/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


PXE boot from an RSA issues

06/24/2015 3504 views
We have around 20 RSA's around the globe all working well but there is one that just refuses to PXE boot.

The machine I am trying to boot from is on the same subnet as the RSA and the DHCP server. The DHCP scope has been set up with option 66 and 67 and everything looks normal.  Booting from a USB works fine but we'd rather avoid that if possible.

Here is the TFTP log:

Jun 25 00:38:28 bei-kace-rsa in.tftpd[83597]: RRQ from 10.3.160.150 filename K2000.0 remapped to k2000.0
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83597]: tftp: client does not accept options
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83598]: RRQ from 10.3.160.150 filename K2000.0 remapped to k2000.0
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83599]: RRQ from 10.3.160.150 filename pxelinux.cfg/420caf89-b17a-64cd-8d77-8396235c4ce7
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83600]: RRQ from 10.3.160.150 filename pxelinux.cfg/01-00-50-56-8c-52-6b
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83601]: RRQ from 10.3.160.150 filename chain.c32
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83602]: RRQ from 10.3.160.150 filename chain.c32
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83603]: RRQ from 10.3.160.150 filename chain.c32
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83604]: RRQ from 10.3.160.150 filename chain.c32
Jun 25 00:38:28 bei-kace-rsa in.tftpd[83605]: RRQ from 10.3.160.150 filename chain.c32

Has anybody come across this?
1 Comment   [ + ] Show comment

Comments

  • trentderby

    3 years ago

     Flag

    OK, an extremely helpful support representative resolved this for me. the issue was with DHCP Option 66 on the Cisco kit, when running this it saw the share as: \\ââ€â€Â¿Ã‹Â¾Y\peinst

    the solution was to bypass this by using a tool called the KBE manipulator, with this we created a new KBE with the IP address hard coded instead of using the DHCP options for the router.

    this allowed us to boot directly into the KBE with no issues.

    if anyone else encounters this issue it will require a support call but you can refer to this ticket number:

    TICK: 258561

     Reply


    This however defeats the purpose... and refuse to go this route making KBEs for each remote site

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ