if (lun > MAX_LUNS_SUPPORTED) {
traceEvent (CONST_TRACE_WARNING, "Cannot track LUNs > %d (for %s),"
"so stats can be tracked for this LUN.\n",
MAX_LUNS_SUPPORTED, dstHost->fcCounters->hostNumFcAddress);
if (isXchgOrig) {
incrementTrafficCounter (&theSession->unknownLunBytesSent,
length);
}
else {
incrementTrafficCounter (&theSession->unknownLunBytesRcvd,
length);
}
return;
}
traceEvent (CONST_TRACE_WARNING, "Cannot track LUNs > %d (for %s),"
"so stats can be tracked for this LUN.\n",
MAX_LUNS_SUPPORTED, dstHost->fcCounters->hostNumFcAddress);
if (isXchgOrig) {
incrementTrafficCounter (&theSession->unknownLunBytesSent,
length);
}
else {
incrementTrafficCounter (&theSession->unknownLunBytesRcvd,
length);
}
return;
}
So you could try adjusting the constant in
globals-defines.h.
(NB: The message text should probably be ...stats can not
be tracked...)
What it will changing it do? No clue - could be a
legit hard limit, or it could be sized as such to limit memory usage for people
w/o iSCSI/FC... Any discussion of this should be in
ntop-dev.
-----Burton
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rueda, Astolfo (SEA)
Sent: Thursday, March 17, 2005 10:56 AM
To: [email protected]
Subject: [Ntop] **WARNING** Cannot track LUNs > 256 (for 49.0f.ef),so stats can be tracked for this LUN.
Does anyone have an idea what this means and how could I fix it so I am able to track LUN stats?
Thank you
Network Administrator
Preston | Gates | Ellis LLP
925 Fourth Avenue,
Suite 2900 Seattle
WA 98104
206-623-7580
206-370-5901
Fax 206-623-7022
“If you obey to rules, you'll miss all the fun”
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
