Show log is also very important , large use in the support. Without it, its very dificult to verify some issues. Another command is sh ip vrf depends on the environment of your end customer. Thanks for all information, nice to add this channel
sh version is ALSO important to identify the current configuration register (0x2102), shows the router UPTIME as a result of a Power hit, or more importantly, the device taking a hit due to a SOFTWARE ERROR. In that last event you'll need to notify your team leader or technical mgmt.
Ronnie you can Show Hist to show the history of the commands that has been issued to the router, now for performance purposes I have used command by directing the output to go to a file and then I would search the file for strings like ip acct, acct, because if IP accounting is turned on for an interface it can literally kill that interface by overwhelming it in utilization, if IP accounting is turned on at the router level "GOOD NIGHT IRENE" that router in most cases will be dead to processing of anything except telling you the IP accounting information. The users of the router will have connectivity and be able to ping the router but no information as far normal business processing will occur due to accounting information capturing. So when you come on your shift to work let be one of the first things you do. Show History and direct the output to a file for you to see if IP accounting has been used. And if so find out why and the duration it needs to be on. And the output from the IP accounting should go to an external drive because it's output can quickly fill up an entire disk or whatever ever type of storage space your using.
Great points! Thanks for sharing your favorite commands! The behavior is probably from overwhelming the buffer on the limited amount of RAM on that device. You're right to send it to a file...this is a better way to tackle this issue.
An exception to this would be to do a IP ACCOUNTING PROTOCOL, showing for a particular protocol or protocols will NOT affect the interface or router as bad, depending on the throughput, but all in all it will impact performance and this should be a privileged instruction also engineers should be the only ones to authorize it's use.
Also front what I have experience there's only one CPU on routers and unless that has changed you need to consider WL Work Load how much is on the CPU utilization & WLM Work Load Mix some internet protocols do Not leave a Routers registers, heaps, and pointers in a home position in other words in a clean and reset to home position that's another issue if your packets follow a protocol that doesn't do good housekeeping with it's procedures you in the same boat packet drops, latency, fragmentation, you know.
Show log is also very important , large use in the support. Without it, its very dificult to verify some issues. Another command is sh ip vrf depends on the environment of your end customer.
Thanks for all information, nice to add this channel
Good point. Thanks for sharing!
sh version is ALSO important to identify the current configuration register (0x2102), shows the router UPTIME as a result of a Power hit, or more importantly, the device taking a hit due to a SOFTWARE ERROR. In that last event you'll need to notify your team leader or technical mgmt.
Thank you for the valuable information as always Ronnie! :)
My pleasure!
Where I can see it
Ronnie you can Show Hist to show the history of the commands that has been issued to the router, now for performance purposes I have used command by directing the output to go to a file and then I would search the file for strings like ip acct, acct, because if IP accounting is turned on for an interface it can literally kill that interface by overwhelming it in utilization, if IP accounting is turned on at the router level "GOOD NIGHT IRENE" that router in most cases will be dead to processing of anything except telling you the IP accounting information. The users of the router will have connectivity and be able to ping the router but no information as far normal business processing will occur due to accounting information capturing. So when you come on your shift to work let be one of the first things you do. Show History and direct the output to a file for you to see if IP accounting has been used. And if so find out why and the duration it needs to be on. And the output from the IP accounting should go to an external drive because it's output can quickly fill up an entire disk or whatever ever type of storage space your using.
Great points! Thanks for sharing your favorite commands! The behavior is probably from overwhelming the buffer on the limited amount of RAM on that device. You're right to send it to a file...this is a better way to tackle this issue.
An exception to this would be to do a IP ACCOUNTING PROTOCOL, showing for a particular protocol or protocols will NOT affect the interface or router as bad, depending on the throughput, but all in all it will impact performance and this should be a privileged instruction also engineers should be the only ones to authorize it's use.
Thanks again for the feedback!
Also front what I have experience there's only one CPU on routers and unless that has changed you need to consider WL Work Load how much is on the CPU utilization & WLM Work Load Mix some internet protocols do Not leave a Routers registers, heaps, and pointers in a home position in other words in a clean and reset to home position that's another issue if your packets follow a protocol that doesn't do good housekeeping with it's procedures you in the same boat packet drops, latency, fragmentation, you know.