TMCheck

TM config check

TMCheck

Shortest form: tmc.

Traffic-manager health checks for Tomahawk 3: IDB and MMU port maps, drop counters, the scheduler hierarchy, a settings file, and an overall health check. The command is present on Trident 3 builds too, but it only works on Tomahawk 3.

Warning

Do not run tmcheck on a Trident 3 switch. It does not check the chip type. It runs Tomahawk 3 code against the TD3 unit, which can fail or crash syncd. On Tomahawk 3 it is read-only.

All keywords must be typed in full. The built-in help shows <idb | mmu> <portmap | drops> <port>. The shell actually takes an optional port bitmap, only after drops (and mmu scheduler); portmap takes no argument.

Unvalidated

drivshell> tmcheck

TMCheck idb <portmap | drops [<pbmp>]>

Check the ingress data buffer (IDB) port map, or report IDB drops per port. By default every port except the management ports is checked. CPU, loopback and management ports print Port :<n> not valid for IDB drops. Tomahawk 3 only; see the warning.

Unvalidated

drivshell> tmcheck idb drops xe0

TMCheck mmu <portmap | drops [<pbmp>] | scheduler [<pbmp>]>

Check the MMU port map, report global and per-port MMU drops (colour, headroom-pool, RQE queue and invalid-destination drops), or show the scheduler hierarchy. Tomahawk 3 only; see the warning.

Unvalidated

drivshell> tmcheck mmu drops

TMCheck settings <file>

Compare the chip’s traffic-manager settings with a reference file. The file is read inside the syncd container. Tomahawk 3 only; see the warning.

Unvalidated

drivshell> tmcheck settings <file>

TMCheck health [<pbmp>]

Run the chip health check and then the per-port check, for all ports or for the given ones. The built-in help shows <all | port>; all works because it is a port bitmap. Tomahawk 3 only; see the warning.

Unvalidated

drivshell> tmcheck health xe0

Built-in help

tmcheck <idb | mmu> <portmap | drops> <port>
tmcheck mmu scheduler
tmcheck settings <file>
tmcheck health <all | port>