Acopia Adaptive Resource Switch Cli Maintenance Manual page 189

The log output can get very verbose. A busy NSM processor may fail if this level is set
too high for too long. You should only use this feature under the strict guidance of
Acopia personnel.
CLI Maintenance Guide
From cfg mode, use the
level for one NSM-log component:
logging fastpath component name level
where
name (1-128 characters) is an NSM-log component from the list of
"NSM-Log Components" on page
level (0-10) chooses the logging level for the component. A 0 (zero) stops all
messages from the component. A 1 causes the component to log
non-recoverable errors only; this is the default. A 2 or 3 adds warnings and
recoverable errors. A 4 adds logs about internal configuration changes.
Levels 5 through 10 add increasing densities of per-packet messages.
The first time you enter any
performance impact. If the warning appears, enter yes to proceed.
This logging level applies to all NSMs that have been enabled for logging with
logging fastpath processor
For example, the following command sets the logging level to 6 (a low volume of
per-packet logs) for the TEM_CIFS component:
bstnA6k(cfg)# logging fastpath component TEM_CIFS 6
bstnA6k(cfg)# ...
Troubleshooting Network Connections
Tracing NSM Processes in the "fastpath" Log
logging fastpath component
7-12, and
command, the CLI warns you about the
logging fastpath
, described earlier.
command to change the logging
7-15