_tshoot-tech-access-broker.html.md.erb

You can [access logs using Ops Manager](https://docs.pivotal.io/pivotalcf/customizing/troubleshooting.html#component_logs)
by clicking on the **Logs** tab in the tile and downloading the broker logs.

To access logs using the BOSH CLI, do the following:

1. Identify the on-demand broker (ODB) deployment by running the following command:

	```
	bosh deployments
	```

1. View VMs in the deployment by running the following command:

	```
	bosh -d DEPLOYMENT-NAME instances
	```

1. SSH onto the VM by running the following command:

	```
	bosh -d service-instance_GUID ssh
	```


1. Download the broker logs by running the following command:

	```
	bosh -d service-instance_GUID logs
	```

<br>
The archive generated by BOSH or Ops Manager includes the following logs:

<table class="nice">
	<th>Log Name</th>
	<th>Description</th>
	<tr>
		<td>broker.log</td>
		<td>Requests to the on-demand broker and the actions the broker performs
			while orchestrating the request (e.g. generating a manifest and calling BOSH).
			Start here when troubleshooting.</td>
	</tr>
	<tr>
		<td>broker_ctl.log</td>
		<td>Control script logs for starting and stopping the on-demand broker.</td>
	</tr>
	<tr>
		<td>post-start.stderr.log</td>
		<td>Errors that occur during post-start verification.</td>
	</tr>
	<tr>
		<td>post-start.stdout.log</td>
		<td>Post-start verification.</td>
	</tr>
	<tr>
		<td>drain.stderr.log</td>
		<td>Errors that occur while running the drain script.</td>
	</tr>
</table>