Tracing Nsm Processes In The "Fastpath" Log - Acopia Adaptive Resource Switch Cli Maintenance Manual

Tracing NSM Processes in the "fastpath" Log

NSM processes can be very verbose on a busy ARX. This slows client/server traffic at
the chosen processor. Use this option only under the guidance of Acopia personnel.
bstnA6k(cfg)# logging fastpath processor 3.1
Enabling TEM logging will adversely impact the performance of the switch.
Are you sure? [yes/no] yes
bstnA6k(cfg)# ...
CLI Maintenance Guide
To debug a connectivity issue, you can trace the software processes on an NSM
processor. A traced NSM processor sends its log messages to a file named "fastpath,"
which is similar to the "syslog" file described in the previous chapter. From cfg mode,
use the
logging fastpath processor
logging fastpath processor slot.processor
where
slot (1-6; 1 on an ARX®1000 or ARX®500) is the slot number of the
desired NSM, and
processor (1-6) is the processor number. Use
list of processors (and their modules and slots) on the ARX.
The first time you issue any
about the performance impact. Enter yes to continue. This prepares the processor for
minimal logging. You can increase the volume of logs for individual processes and
process groups on the NSM, as shown below.
For example, the following command configures NSM processor 3.1 for logging:
Troubleshooting Network Connections
Tracing NSM Processes in the "fastpath" Log
command to choose an NSM processor to trace:
command, the CLI issues a warning
logging fastpath
for a complete
show processor
7-11