![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
LANDesk(R) Management Suite v2.x: Performance Monitor Usage Tips
Contents:
"CANNOT ATTACH TO DEVICE MLID.COM AT I/O PORTNUMBER"
Symptom:
When you launch Traffic Monitor, Performance Monitor, Traffic Analyst,
Application Monitor, or Software Probe in LANDesk(R) Manager Suite v2.0,
you get an error message something like "Could not attach to device
E100ODI at I/O FCCO" or "Cannot attach to device NE2000 at I/O 300" even
if TESTPRO.EXE reports that the driver supports promiscuous mode. (The
I/O address is not relevant.)
Description:
Novell has released a new version of their ODI specification, v4.
LANDesk(R) Management Suite does not yet support the new ODI v4 spec.
Solution:
The normal workaround is to go to an older LSL and MLID (based on ODI
v3). For the new Intel EtherExpress PRO's and TokenExpress PRO's, these
older drivers may not be available.
One potential workaround is to turn off "Auto Name Resolution" in
Traffic Monitor under TOOLS | ALIAS NAME TABLES. You can also try
increasing the VmonPacketHeap= setting the your SYSTEM.INI from the
default of 5000 to 10000 or more. If this doesn't work, you may need to
use another NIC that has an older MLID as your data collection device.
MULTIPLE LAUNCHES OF PERFORMANCE MONITOR
In order to run multiple instances of the application from the network
the user needs to specify a dir=(some different directory location) in
the ldpm.ini file under the appview section. Also the user will need to
copy the *.adf file to this new location. If a separate directory is
not specified both apps will be trying to write similar infomation to
the same log file.
Note: That the probe doesn't have this problem because it uses its
own card to do the collection.
"ILLEGAL FUNCTION CALL"
This message appears to the second, third, etc. person to simultaneously
run Performance Monitor, then exit it. They receive size errors from
PMLOG01.ALF.
In order to run multiple instances of the application from the network,
the user needs to specify a dir=(some different directory location) in
the LDPM.INI file under the appview section. Also the user will need to
copy the *.adf file to this new location. If a separate directory is
not specified both apps will be trying to write similar infomation to
the same log file.
Note: That the probe doesn't have this problem because it uses its
own card to do the collection.
Trademark information