![“I have just pulled out blade 5, lets look the internal ports…”](/images/new-backgrounds/124896/1248967x1.webp)
All the way through the capture, type (just at the CLI prompt) what you are thinking, and what you are doing. Just write it as
“Hmmm.. that counter value looks strange, lets look at this a bit more”
“I have just pulled out blade 5, lets look the internal ports…”
“Right, the ping to the PC on port 5 just starting failing “.
Of course, your consciousness might not stream in English. If so, then write the comments in your language; the important ones can always be translated later. The important thing is that the writing of the comments does not get in the way of the job at hand.
Of course, writing comments at the CLI prompt will mean that you get error messages from the unit like:
Manager > Now I am going to send the IGMP report from the client, and see if any PIM counters or states change
Error (3035256): Unknown command "Now".
But that is quite OK, the person analysing the capture will be able to mentally filter out these error messages.
When you see something really significant, you might want to highlight it, so it is easy to find later. A string of !!!!!!!! or ###### are good ways to make sure something stands out when you are browsing through the file.
What counters are changing?
Often, the investigation of a theory requires looking for what is
Concrete piece of advice #4: Perform particular show commands a few times in succession.
You might see certain values changing that give a vital clue to what is happening. Or, if you don't notice them, the person analysing the capture after you might.
Rate of change can be important
More subtly, the rate at which certain things change can often be
Concrete piece of advice #5: If you are investigating matters that are
4