325
edits
Generic troubleshooting processes: Difference between revisions
Generic troubleshooting processes (view source)
Revision as of 15:15, 16 December 2021
, 16 December 2021no edit summary
Remco.derooy (talk | contribs) |
Remco.derooy (talk | contribs) No edit summary |
||
| Line 211: | Line 211: | ||
* Applications that are too slow or problematic and therefore are unable to keep up | * Applications that are too slow or problematic and therefore are unable to keep up | ||
* Storage that is too slow or problematic, and therefore is unable to keep up. | * Storage that is too slow or problematic, and therefore is unable to keep up. | ||
== IP statistics (all) == | |||
If you are looking for network information based on multiple or all IP addresses, or want to start your troubleshooting journey from an IPs perspective – the L3 IP Statistics page is the right place for you. | |||
[[File:L3- IPs.png|1100x1100px]] | |||
IPs (of interest) can quickly be found, by entering (part of) an IP or resolved-name information. When searching for a singular IP or IP-range, add a subnet mask to the IP for optimal results. E.g. searching for 192.168.178.1 will give you a filtered list with all IPs matching 192.168.178.1xx. To mitigate this, add a subnet mask like so 192.168.178.1/32. | |||
On the IP Statistics page, it is also possible to only present IPs that match certain (quality) metrics. To start filtering with a “complex filter”, start your entry in the search bar with a "(". The next possible inputs are then shown to you, as a form of help. By using a “complex filter” in the search bar, you can narrow down the number of displayed IPs, based on the following parameters: | |||
"name", "ip", "packets", "bytes", "pps", "bps", "firsttime", "lasttime", "tcppackets", "udppackets", "tcppayload", "tcpRetrans", "tcpRetransRx", "tcpRetransTx", "category", "vlan", "mpls", "outermpls", "innermpls", "interface", "validconnections", "invalidconnections", "tcpZeroWindowRx", "tcpZeroWindowTx", "ipgroup", "mtu", "mtuRx", "mtuTx", "tcpMissedData", "(" | |||
The use of and/or/must contain/exact match operators is allowed in the form of: AND, &&, OR, ||, ==, === | |||