[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

2341.0. "PROBEwatch T3.2 for Digital UNIX hints" by SSSAXP::LEMONS (And we thank you for your support.) Sat Jun 03 1995 03:32

    Hi
    
    I've copied and installed PROBEwatch T3.2 for Digital UNIX.  I did read
    in the .PTR file that documentation isn't available.  I've never used
    PROBEwatch before, so don't have a clue on how to start it.  I'll look
    forward to the documentation, but could I have a few hints, just to get
    going?
    
    Thanks!
    tl
T.RTitleUserPersonal
Name
DateLines
2341.1Starting PROBEwatchNETCAD::FORINOMon Jun 05 1995 14:1119
    
        Here's instructions I received.
    
	TO Start PROBEwatch:
	
		cd /usr/kits/PROBEwatch
		(source .netscout ; bin/nsma)

	The .netscout file is a small shell script that contains commands 
	to set enviornment variables that are used by PROBEwatch..  This
	file (list of commands ) may be appended to your .cshc file ..

	ex.
	
		cat .netscout >> `/.cshrc
    
    
    						John
2341.2simple quickstartNAC::FORRESTMon Jun 05 1995 15:3246
    
    One approach until we get Online Help into the OSF version, would be to
    copy over and install the Windows kit, then use the online help in
    there. Otherwise, here's a real simple quickstart.
    
    
    Step 1: Click on the Add button to add your probe(s) to the table. If
    	    you have more than one probe, you might want to add a Group
    	    Name.
    Step 2: Click on Test to make sure it is reachable, and that you have 
            the community strings correct.
    Step 3: Click on Domain Manager to install the domains for the 
    	    protocols you want to monitor; (the ALL domain records all 
    	    of the Ethernet traffic.
    Step 4: Use Protocol Monitor or Traffic Monitor to see what's 
    	    happening on the segment.
    Step 5: Use the Tools pulldown menu to look at Host and Converstation
    	    data.
    Step 6: Use Data Capture to setup the probe to capture packets and 
    	    Protocol Decode to look at the captured data.
    
    Other notes: The Remote Login button sets up a remote console session 
    	    with the probe. 
    
    	    The Token Ring Monitor button only applies to TR probes.
    
    	    The Resource Manager button brings up a screen, but you can't 
    	    do anything there unless you have a Frontier NETscout probe 
    	    with the Resource Manager option.
    
    	    The Alert Manager button brings up a window for viewing Traps 
    	    that have come in. To set Thresholds and generate Traps when 
    	    a threshold has been crossed, use the Watchdog function from 
    	    the Tools pulldown that appears on some of the domain-specific
    	    screens.
    
    	    The Filter Editor allows you to specify custom protocol filters
    	    for data capture or for creating new domains.
    
    	    The Domain Editor allows you to create new protocol domains,
    	    which can be made up of 1 or more filters.
    
    	    The NETscout shell button brings up a screen to issue command
    	    line scripts to a probe. Type Help for a list of commands; type
    	    a command to see the syntax for its use.
    
2341.3CRONIC::LEMONSAnd we thank you for your support.Mon Jun 05 1995 21:324
    Thanks for taking the time to post this!
    
    tl