Table of Contents
Advertisement
Troubleshooting Network Connections
Tracing NSM Processes in the "fastpath" Log
2006-11-22T08:43:30.000+0000:bstnA6k:3-2-NSM_TX-2124:NET_APP-0-7-MSG7:: cifs_proxy.c:415:
cifss-conn:CIFS connection DOWN event. Client:192.168.25.15:53711
7-20
NSM-Log-Message Syntax
Each line in the fastpath log file uses the following syntax:
utc.uuu+tz:switch:slot-proc-board-pid:cmp-ins-sev-id:: msg
This is the same format as is used in the syslog file (recall
page
6-16). For example,
Where
•
utc (2006-11-22T08:43:30 in the example) is the time in UTC.
•
uuu (
) is the millisecond time fraction.
000
•
+tz (
) is the hours off UTC (+nnnn or -nnnn).
+0000
•
switch (
) is the switch name.
bstnA6k
•
slot-proc-board (
3-2-NSM_TX
type (always NSM). Use the
processors and their associated modules.
•
pid (
) is the Process ID (PID).
2124
•
cmp (
) is the log-component name. Refer to
NET_APP
on page
7-12.
•
ins (
) is the process's instance number.
0
•
sev (
) is the message severity, from 7 (debug) to 2 (critical).
7
•
id (
) is the message-catalog ID, a unique ID for each log message. MSGn is
MSG7
an ID for an uncataloged message. The n is the severity of the message, from 7
(debug) down to 2 (critical).
•
msg (
cifs_proxy.c:415: cifss-conn: CIFS ...
itself.
) is the chassis slot, processor number, and board
command for a list of all
show processors
"Syslog Syntax" on
VIP:192.168.25.15:139
"NSM-Log Components"
) is the message text
CLI Maintenance Guide
Advertisement
Table of Contents
Troubleshooting
