Create Deployment Media

Usage and Config OSD
1

I’m trying to Create Linux Network boot Media to install targets without PXE boot. The Linux OS Resource is SLES 11 SP 3. The second step of Action:GenerateLinuxDeploymentMedia - Create Deployment Media ran for 51/2 hours and failed on the last step with this error:

Failed continue if {exists file ((parameter “AGENTFOLDER” of action) & (parameter “LOGFILENAME” of action)) whose (exists lines whose (it as string contains “[AGTRC:0]”) of it)}
regset “[HKEY_LOCAL_MACHINE\Software\BigFix\EnterpriseClient\OSDControl]” “SyncTimeMedia”=“1510172500258”

The log file - rad-temmklinuxbootcd.log.1510172500248 - follows: Can you help with cause of the error?

Bare Metal Server for IBM BigFix OS deployment Web extension 64 bits v.7.1.1.20 (300.15)
Licensed Materials - Property of IBM. L-PSCN-7SXJVW
© Copyright IBM Corporation 1998, 2017.
All Rights Reserved. IBM, the IBM logo, and Tivoli are trademarks
of IBM Corporation in the United States, other countries or both.
Bootable: \.\PHYSICALDRIVE0
Server ipaddr =
Found exact Interface, ipaddr =
Server probing skipped for Interface, ipaddr =
Connect ->
Device \.\PhysicalDrive0 (0:0) is a regular disk
Device size: 209715200 KB
Hard disk geometry: ff 3f
Non-USB: \.\PhysicalDrive0
Device \.\PhysicalDrive1 (0:1) is a regular disk
Device size: 209715200 KB
This disk geometry: ff 3f
Non-USB: \.\PhysicalDrive1
File server not responding
A Packages not found at path net://global/rad/rbagent.pak: retrying…
Attempt 1/6 to load packages
Waiting 30 seconds before retrying
File server not responding
A Packages not found at path net://global/rad/rbagent.pak: retrying…
Attempt 2/6 to load packages
Waiting 30 seconds before retrying
File server not responding
A Packages not found at path net://global/rad/rbagent.pak: retrying…
Attempt 3/6 to load packages
Waiting 120 seconds before retrying
File server not responding
A Packages not found at path net://global/rad/rbagent.pak: retrying…
Attempt 4/6 to load packages
Waiting 120 seconds before retrying
File server not responding
A Packages not found at path net://global/rad/rbagent.pak: retrying…
Attempt 5/6 to load packages
Waiting 120 seconds before retrying
File server not responding
A Packages not found at path net://global/rad/rbagent.pak: retrying…
Attempt 6/6 to load packages
A A A (called from --toplevel-- (rbagent.rbc:4814))
Stopping Web extension
Error raised by LoadTPMfOSd in rbagent.rbc, line 4509 [:0]
Connection refused (Failed to load packages (net://global/rad/rbagent.pak) [AGT:4509])

1 Like
2

Hello, first thing we suggest to try is change the default Tcp port for Http requests from 8081 to 8080. For doing the change, open the OSD Bare Metal Server GUI and go to
Server Parameters->Server Configuration. Edit Web Interface Parameters and change
TCP port for HTTP request. The default is 8081, change it to 8080. Retry the scenario and let us know

3

You have to restart bare metal server to have the change effective

4

HI, I’m not familiar with the OSD Bare Metal Server GUI. Can you send me the path to the executable? thanks.

5

Start --> All Programs --> IBM Tivoli Provisioning Manager --> Web interface

6

Hi, The web interface - http://127.0.0.1:8081/ returns “This page can’t be displayed”.

7

hello, you should check if the Bare Metal Server Service is up and running and in case
you can try to stop it and start again. If you have problem in starting the bare metal service
collect the c:\TpmfOS Files\logs (we can check therein traces if the service has problems in starting).
If after the restart you still have problem opening the Bare Metal Server GUI, open a field case providing the c:\TpmfOS Files\logs

8

Thanks for your help. The web page is accessible after restarting the OS Deployment Server. Now I just need a login :wink:

9

You should have specified the credentials when you installed the Bare Metal Server. The logon account and a hashed password are in the .conf files, which IIRC are rembo.conf and rbagent.conf, and stored in \Program Files\Common Files\IBM (something).

If you need to reset the credential, there are probably easier ways to do it but I’ve installed Bare Metal server on another host, with known credentials, and copied the hashed password into both the server (rembo.conf) and client (rbagent.conf) files. Restart the Bare Metal Server, regenerate your PE resources and deployment media, and you should be good to go.
Needless to say, make backup copies of any files you modify this way.