Conference netcad::hub_mgnt

> Has anyone used Probewatch to monitor generic RMON capable devices.
> <deletions>
> Any help or experiences welcomed.


I haven't tried this, but I can speculate.

RMON interoperability appears to be an illusion.  PROBEwatch does not
interoperate well with RMON agents.  PROBEwatch also makes extensive
use of private (non-RMON) objects for "value-added" features like
domains.  The private MIB objects give them RMON2-like capabilities.
When RMON2 comes out, there will be a different set of interoperability
problems.

I don't know if other vendors do better at RMON interoperability.

So, I doubt PROBEwatch can interoperate with Cabletron boxes.  We've
had enough trouble trying to get PROBEwatch to interoperate with our
products.

Someone else will have to address your PROBEwatch configuration questions.

						-Shawn

    As Shawn mentioned in .1, all RMON are not created equal. Frontier
    (creator of PROBEwatch / NETscout) uses  what they refer to as Domains.
    Not all vendors support the Domain concept.  For interoperability, the
    only "Domains" that may work between vendors is the ALL Domain (which
    will be the RMON domain in a future release).
    
    If you put an analyzer (say IRIS) and trap for SNMP packets you'll see
    the mib gets that PROBEwatch/NETscout does.  I have not done this in a
    while, but they were going after some proprietary mib values making the
    software unfriendly to nonDigital / Frontier probes.  
    
    Try editing the /usr/kits/PROBEwatch/usr/protmon.cfg and use only the ALL
    domain.  
    
    It's a good idea to keep dvinst.cfg consistent with the protmon.cfg
    file. dvinst.cfg is the default configuration file that will be used
    load domains for the probe (provided the server address points to a
    system running PROBEwatch/NETscout).  This won't apply to the
    cabletron...
    
    
    When the protocol monitor is run, it will check the protmon.cfg file to
    ensure that the domains it expects are installed. If they are not, the
    management software will attempt to install the domains (which will
    fail on the cabletrons). If ALL won't work try RMON as the Domain.
    
    
    Technically Elite (TEC - now in Campbell California) recently won a
    couple awards for their Meterware software at this past Interop (Best
    of show awards) for RMON analyzers.  They tout their interoperabilty,
    but I've never tried to manage specific element managers with their new
    software.
    
    
    							rick

    OK, now a more directed question:
    
    	Will clearVISN RMON Manager, talk to and work well with the:
    		DECpacketprobe90 (Ethernet)
    		DECpackatprobe900RR (Token Ring)
    		DECswitch900 RMON 4-group
    		DECswitch900 RMON 9-group upgrade
    		FRONTIER Probes with new Digital "DT-" part numbers?
    
    Anyone?
    
    Mark

   Having an opportunity to experiment on the customers system, I renamed
Traffmon.cfg (or it could be edited to remove Domain: ALL), and tried to
access a Cabletron EMME with Traffic monitor.

   After a couple of false starts it worked fine, with long and short term
history graphs available also.

     Richard.

    How about the other side of the coin:
    
    	My customer, INS, just bought a number of our 900 switches with the
    RMON 9-group upgrade. They plan to 'talk' to the RMON agents with their
    existing SUNnet MGR, RMON utility. They do NOT want to buy our
    clearVISN RMON manager unless absolutely required.
    
    Will OUR 9-GROUP RMON agents work with a non-Digital RMON utility?
    
    Mark

I installed clearVISN RMON Manager on a Token-Ring site, where they had a
HP Probe of some kind on their Token-Ring network. 

I launched RMON Manager and started the Token Ring Moinitor and a number of 
parameters and counters were displayed. The customer were impressed, and I 
got a confirmation on my theories about interoperability, some works some don't.

Bj�rn Olav Haugom