PXE Imaging

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #186
    Avatarfauxone01
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    I’m having problems when testing the image process for a 941GXL device in Rapport. The device appears in Rapport so as an initial test I tried a “get device image” job. The package appears in the “Images” section of Rapport and a job is created in “Scheduled Packages” awaiting the device reboot in order to create the actual i2d file. For some reason when the device PXE boots it grabs an ip but then skips straight to “local boot” and starts up Windows rather than pushing the image file to the Rapport server via tftp.
    The device is on a separate vlan to the Rapport server so I had the network guys add an ip helper for the server address. I also had them ensure that portfast is enable as we have Cisco switches in place.
    Has anyone come across this before? It’s a worry that I’m having these issues now as I have to make this work over our MPLS WAN once I’ve proved it works on the LAN. That will surely lead to a whole nother world of pain.
    Thanks in advance for your assistance.
    Fauxone01

    #8814
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    I have seen this before and it turned out that there was something else using IIS on the Rapport server and this caused it to fail. (in that case insight manager)

    Try this simple test, plug the device on the the same VLAN as the Rapport server and try the pull again, did it work? (trying to eliminate network issues here)

    As for MPLS WAN links, I am writing and artical on this but really you need Rapport Enterprise for this. Pushing 512MB images over WAN links sucks and you can only do 5 images at a time with Workgroup. With enterprise you use a local ftp server to hold the images so it pulls locally – much better.

    Let me know how the test goes…

    #8826
    Avatarfauxone01
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    TT,

    I’ve got Rapport Enterprise installed and have managed to get devices pulling and pushing images on the LAN however I’m still having issues over the WAN.
    When I schedule a job for a remote device it begins the task, reboots and obtains an IP address from DHCP here in London. Once it has an IP it should begin the PXE boot task (as it does successfully on the LAN) but instead the message “Local Boot” appears and Windows XPe boots as normal leaving the scheduled job still waiting in Rapport. We have the necessary ip helpers in place so I’m not exactly sure what is preventing this from working. I’ve done countless Ethereal traces trying to determine where its going wrong but can’t quite work it out. The last traffic we see from the client is the DHCP request/ack process but I guess the device is unable to determine that Rapport has a job waiting for it.
    We originally installed Rapport using an MSDE however I have logged a request with our DBA team to migrate it to SQL (using your helpful tips!). Once this is done I’ll take your advice and use a remote repository instead of attempting to send images across the wire. First we need to get these PXE clients working correctly though.
    Thanks for you assistance…again! I don’t know how we survived before your site!

    Cheers
    fauxone01

    #8828
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    I agree it is a network issue here, the fact you can pull/push an image locally means we can assume the Rapport server is OK. PXE over WAN’s can be a pain!

    Right, what we need is a ethereal trace on the client and the Rapport server so we can look for the following:

    – Did the Rapport server actually recive the DHCP req. Packet from the device (check the MAC ID)
    – What response did the Rapport server give?
    – Did this response make it back to the client in tact?

    On know this is a bit of work to trace but it will be the quickest way to track the problem down. If you are not sure what comunications should happen do the tests on the local LAN to see a working PXE exchange and then repeat the tests on the problem VLAN. If you get some nice Ethereal captures you can email them to me,

    Cheers,
    -TT

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.