After a hub is upgraded to 7.x, some probes stop working and show a message in the logs"
Command hubpost_bulk not in command-list in probe logs.
Example from Logmon:
Apr 13 20:05:57:465  logmon: RREQUEST: hubpost_bulk <-18.104.22.168/48002 h=236 d=9520
Apr 13 20:05:57:465  logmon: data bulk_size=1 bulk_list=PPDS(9467) qsize=1
Apr 13 20:05:57:465  logmon: Command 'hubpost_bulk' not in command-list
Apr 13 20:05:57:465  logmon: SREPLY: status = 11(command not found) ->22.214.171.124/48002
To resolve this issue two new keys need to be added to the hub in raw config:
bulk_size_floor = 1
default_bulk_size = 1
This is happening as Hub 7.x tries to disallow a bulk size of 1 and imposes a "floor" of 100 whenever it thinks the consuming probe supports that.
e.g., logmon was trying to make a connection to the hub. Because the hub was trying to force the connection to use a minimum bulk size of 100 it was causing a problem. By changing the hub to allow it to default back to 1 resolved the issue.
keywords: bulk_size_floor default_bulk_size hubpost_bulk command-list