Mike Raineri

@dan-m-joh is correct; the first thing would be to try checking that Redfish is enabled. You could also attempt to access Redfish in a browser or Postman to see if...

@wushuzh I created the branch "Add-Library-Trace-Support" to capture what's going on. If you run the tool with the newly added `--trace` option in that branch, it will capture all HTTP...

@wushuzh you will need to look in the `rf-mockup-create.log` file in the output directory for the additional trace info.

Yes, `/redfish/v1/` is a mandatory URI and is used for service discovery. It's also needed to find all supported resources in the service, and find the session collection in order...

Are you able to access `/redfish/v1/` from your browser? Is there a timeout message, HTTP response of some sort, or other trace after all of the retries? The message "Name...

It's entirely possible it's IPv6 related; I haven't tried using the tool (and Redfish library) with an IPv6 target before. I'll see if I can find a device on IPv6...

@jcleung5549 to follow up and see if we can track down what to do with this issue...

Moving issue; looks like a problem with the profile simulator and not redfishtool.

This is due to how Volume is ultimately produced by SNIA, but the DMTF republishes the file in its 8010 package. Unfortunately there may be gaps in time where the...

Are you only copying over Volume, or everything SNIA has published? I tried Volume 1.8.0 and did not recreate the exception.