| Next revision | Previous revision |
| wiki:tower_networking_inc:devices:debugger [2025/08/20 14:03] – created poco | wiki:tower_networking_inc:devices:debugger [2025/08/20 14:49] (current) – poco |
|---|
| ====== DEBUGGERS ====== | ====== DEBUGGERS ====== |
| |
| **Device Debugger** | Device Debugger |
| |
| ===== The Debugger Device ===== | The <color green>debugger device</color> is a 2-port device used to allow troubleshooting and configuration tasks using the <color green>netsh</color> application. To <color green>configure or troubleshoot a device</color>, a debugger must be powered and a network route must exist <color green>between the debugger and the device</color>. It is a good idea to place the debugger in your datacenter and connect it directly to your core switches to allow a single debugger to troubleshoot/configure your entire datacenter. |
| |
| The debugger [color=skyblue]device[/color] is a 2-port device used to allow troubleshooting and configuration tasks using the [color=skyblue]netsh[/color] [color=skyblue]application[/color].\n | The figure on the right shows a direct connection setup from the debugger to a device. This allows the debugger to execute commands on this device. |
| \n | |
| To configure or troubleshoot a device, a debugger must be [color=skyblue]powered[/color] and a [color=skyblue]network route[/color] must exist between the debugger and the device.\n | |
| \n | |
| It is a good idea to place the debugger in your datacenter and connect it directly to your core switches to allow a single debugger to troubleshoot/configure your entire datacenter. | |
| |
| The figure on the right shows a direct connection setup from the debugger to a device.\n | A slightly better setup is to wire the debugger through a switch. This allows the debugger to execute commands on every device connected through the switch. In the example to the right, the debugger will be able to debug and configure both device A and device B without needing to change the cabling setup. |
| \n | |
| This allows the debugger to execute commands on this device. | |
| |
| A slightly better setup is to wire the debugger through a switch. This allows the debugger to execute commands on every device connected through the switch.\n | To see the list of debuggers currently accessible, use the <code>lstdbg</code> command. This will show a list of debuggers and their logical address. You can then see the list of devices that are accessible by the debugger using the \<code>scan</code> command; if the debugger address is <color orange>63168</color>, then input <code>scan devices using 63168</code>. The scan command shows a list of device that are accessible by the debugger and their corresponding network address. Using the <code>watch</code> command on the listed device addresses, detailed information about the device can then be seen on the debugger. For example, if the scanned device address is <color orange>41216</color>, then input <code>watch 41216 using 63168</code>. |
| \n | |
| In the example to the right, the debugger will be able to debug and configure both device A and device B without needing to change the cabling setup. | |
| |
| \n | It may be unwieldly to keep typing address of the debugger if you always debug from the same debugger. Use the <color green>always routine</color> command to set the default debugger to use. For example, given that the debugger address is <color orange>51727</color> and we always want to use that, input <code>always using 51727</code>. This allows you to then type any debugger related commands without the <code>using ...</code> part. This means that instead of typing <code>scan devices using 51727</code>, you would only need to type <code>scan devices</code>. |
| To see the list of debuggers currently accessible, use the \"lstdbg\" command. This will show a list of debuggers and their [color=skyblue]logical address[/color].\n | |
| \n | |
| You can then see the list of devices that are accessible by the debugger using the \"scan\" command; if the debugger address is 63168, then input \"scan devices using 63168\".\n | |
| \n | |
| The scan command shows a list of device that are accessible by the debugger and their corresponding network address.\n | |
| \n | |
| Using the \"watch\" command on the listed device addresses, detailed information about the device can then be seen on the debugger. For example, if the scanned device address is 41216, then input \"watch 41216 using 63168\". | |
| |
| It may be unwieldly to keep typing address of the debugger if you always debug from the same debugger.\n | |
| \n | |
| Use the [color=skyblue]always routine[/color] command to set the default debugger to use.\n | |
| \n | |
| For example, given that the debugger address is 51727 and we always want to use that, input \"always using 51727\".\n | |
| \n | |
| This allows you to then type any debugger related commands without the \"using ...\" part.\n | |
| \n | |
| This means that instead of typing \"scan devices using 51727\", you would only need to type \"scan devices\". | |
| |
| \n | You can always refer to the <color green>netsh</color> guide for help. Always remember that the command <code>man</code> (short for manual) is a useful way to find out more about a command. To use the command, simply type \<code>man</code> or <code>man <name of program you want to find out></code> |
| \n | |
| You can always refer to the [color=skyblue]netsh[/color] guide for help. Always remember that the command \"man\" (short for manual) is a useful way to find out more about a command. To use the command, simply type \"man\" or \"man <name of program you want to find out>\" | |
