[Intel Navigation Header]

    LANDesk(R) Management Suite v2.x: Probe/PRCM Usage Tips

    Contents:

    • CONTENTS
    • "CANNOT ATTACH TO DEVICE MLID.COM AT I/O PORTNUMBER"
    • AUTO-LAUNCHING PRCM FROM TRAFFIC MONITOR OR PERFORMANCE MONITOR
    
    

    CONTENTS

    
       This document discusses issues commonly encountered with Software Probe
    
       and PRCM.EXE.  It supplements the files in LANDesk(R)  Management
    
       Suite's Readme Viewer.
    
    
    
    

    "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.
    
    
    
    

    AUTO-LAUNCHING PRCM FROM TRAFFIC MONITOR OR PERFORMANCE MONITOR

    
       When the "auto-launch PRCM" option is selected, the next time you run
    
       either monitor tool you are not prompted to select a device.  It still
    
       comes up using the administrator stations' NIC. You must select a remote
    
       probe from the TOOLS | SELECT DEVICE option.
    
    

    Trademark information