Conference netcad::hub_mgnt

    
    
    For testing, we're going to one specific osf node (a 2100).
    
    I first had him go through snmpsetup again.
    The results changed. Now instead of it saying "cannot build complete
    path" twice, it gets TO the system and then gives the error "cannot
    build complete path". 
    
    Traceroute shows 1 hop to the system. Got on the 2100 and did a
    traceroute back to the pathdoctor station and that was also only one
    hop. 
    Route tables on both systems look ok. 
    On the 2100, there is a tuo and a couple of Sl0s. The 2100 is running
    3.2b. The release notes talk about unnumbered ip addresses, but the
    sl0s don't show up in the route tables so shouldn't come into play...
    (or should they??)
    
    Hum...ok, I had him demand poll it under Netview. We got back
    GetInterfacesTable: Interface serial does not have an IP address. Is
    this what's messing up pathdoctor?? It does seem to go along with what
    the release notes are saying....
    But what does this mean to a cuatomer who has hundreds of alpha
    stations?
    
    thanks
    

    So, what's a path doctor?
    
    
    md

    Sounds to me Mike that a path doctor is a tool to find alternate
    logical network paths between end nodes.
    
    Bob

    
    
    Polycenter Path Doctor......
    
    I saw one note in here about the latest shipped version, and since
    there doesn't appear to be a note specific to PathDoctor, I assumed
    that this was the right place?
    
    PathDoctor (in my opinion) is just traceroute in color.... ;-)

Wrong place. Path Doctor is from the folks down the hall.  It's not us!

A few years ago, it was the people who are now the ManageWorks group that
were working on Path Doctor. Check with them. (Is there a ManageWorks
notesfile?)

Tom

    I looked it up in the most recent easynotes.lis file I have.
    There's a manageworks notes file listed at noted::mwdev.
    
    Bob

    
    
    thanks!

Cathy,

there is a (not very active) notesfile for pathdoctor, it is on MARX::PATHDOCTOR.
This tool was very promissing when it was introduced, unfortunately it has not
evolved since then.

I think that the Router Manager Application which will be part of ClearVISN will
provide similar capabilities (I hope).

Manuel.

================================================================================
Extract from the SPD (may 1994):

 PRODUCT NAME:  POLYCENTER PathDoctor, Version 1.0      SPD 51.29.00

 DESCRIPTION

 POLYCENTER PathDoctor is an interactive SNMP-based network management
 software tool. It assists users in evaluating the health and perfor-
 mance of IP routing paths between specified TCP/IP address pairs. Ver-
 sion 1.0 of PathDoctor runs on the DEC OSF/1[R] AXP and DEC RISC/ULTRIX
 platforms.

 POLYCENTER PathDoctor is designed for WAN and extended LAN environ-
 ments that route IP network traffic through routers supporting the Sim-
 ple Network Management Protocol (SNMP). PathDoctor is particularly adept
 at determining routing problems and inefficiencies for Cisco, Wellfleet,
 3Com, Proteon[TM], Digital, and IBM[R] routers.

 POLYCENTER PathDoctor V1.0 graphically displays the end-to-end path
 between any user-specified pair of IP addresses. It provides real-time
 information regarding the configuration, health, and performance of
 the various interfaces and nodes in the path. It is a smart tool that
 has built-in knowledge that allows it to understand and use available
 SNMP standard and private network management information.

 PathDoctor identifies interfaces and nodes in the path that are hav-
 ing data forwarding problems and displays a color-coded status of those
 interfaces and nodes. For example, PathDoctor can identify when a Cisco
 router's IP module is discarding more than 1.5% of good traffic be-
 cause of buffer allocation failures.

 Using PathDoctor's logging capability, the user can log the percent
 of good traffic discarded by the IP module and the corresponding val-
 ues for buffer allocation failures. This log will allow the user to
 see whether the rule for discarding good incoming traffic was trig-
 gered due to an unusual spike or if the values were consistently close
 to the threshold value over time.

 A typical PathDoctor scenario is when a user is experiencing IP per-
 formance problems between two remote system and reports the problem
 to network support. With PathDoctor, technical support can easily de-
 termine the forward and reverse paths between the two systems and un-
 cover within minutes whether any component along that path is expe-
 riencing routing or forwarding performance problems.

 PathDoctor is very simple to use in its identification of IP router
 and interface problems and operations. With PathDoctor, users of all
 technical levels gain greater insight in the operations and effective-
 ness of their IP networks reducing network inefficiencies and improv-
 ing network operations.

 POLYCENTER PathDoctor can be used standalone, or in conjunction with
 the POLYCENTER Manager on NetView