I was thinking of possibly trying to do the scratch folder creation via a PowerCLI script that runs after hosts are deployed but i'm not sure if this is possible or not?
I guess it is using esxcli
system coredump partition set --partition="/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0:7"
system coredump partition set --enable=true
I have similar questions, can someone help out with this thread?
I’ve setup one of our hosts to boot from SD, and have pointed the scratch file to one of our DataStores. My next questions are:
1. If I were to point all of our host scratch files to one DataStore, can I use a variable (such as hostname) in the path that I enter on the Advance screen in the “ScratchConfig.ConfiguredScratchLocation” field?
a. Example: /vmfs/volumes/4f67f949-479840f2-c390-0025b3b1ce8f/$hostname
2. What happens to this setting when we use Host Profiles? Does it carry over when applied to a host, or something we have to set each time, per host.
3. If it is carried over with host profiles and we can use a variable as above, will this path with the variable be carried over to the hosts once the host profile is applied.
So the solution to this was to set the Advanced Configuration option > Syslog.global.logDirUnique as enabled (ticked) Then for each host the hostname will change as each folder is named as the hosts name. It applies across with host profiles no problem.
I don't think this is correct. This will change the output of your logs but not of the scatch partition (where your core dumps go). You would need to specify this advance option to change the core dumps: ScratchConfig.ConfiguredScratchLocation: This will update the coredump location. You can validate by SSH into one of your systems and do a ls -la from the / location to see if the symbolic link and updated correctly. Also, you should see the core folder in the datastore that you have assigned to the location.
You can see I routed my Syslog.global.logDirUnique also to go into the same subfolder as well.
after playing around with this, i confirmed what GMAN said to be true....the syslog settings only control those settings....not scratch settings. However, I'm confused about the differences between scratch and syslog. Can someone explain the difference? I'm guessing that the scratch partition is written to during a crash situation and/or if syslog is not available and hence the need for both?