| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE | 
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 | 
| Moderator: | NETCAD::COLELLA DT | 
| 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 | 
Hye,
    
    We use the new version of Probewatch Ultrix (2.5.3) at the French
    Network Control Center in Evry, and we have some questions about it :
    
    - How can we do to configure different trap destinations (with watchdog
    option) in this version ?
    
    - Where can we find the 'Frontier' mib for the DECpacketprobe90 ?
    
    Moreover, we would like to know the location of the new Probewatch
    manual ( for the reporting use in particular -> msg :"nsrpt: No reports
    available for agent...") because TNPUBS::PUBLIC$DISK:<PUBLIC.ONEHUB>
    seems not to be correct. 
    
    Thanks for your help.
    
    Jacques M.
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 1061.1 | configuring multiple TRAP destinations | NAC::FORREST | Thu Aug 11 1994 22:14 | 18 | |
| >>    We use the new version of Probewatch Ultrix (2.5.3) at the French
>>    Network Control Center in Evry, and we have some questions about it :
    
>>    - How can we do to configure different trap destinations (with watchdog
>>    option) in this version ?
A separate utility, dvadmin, is required. Copy the file
NAC::NIPG:[MANAGE.RMON]DVADMIN.TXT for details.
  
>>    - Where can we find the 'Frontier' mib for the DECpacketprobe90 ?
I do not have the Frontier MIB, but most features use the standard RMON MIB.
See note 842.11 for how to make the DECpacketprobe work with SNMP managers 
other than PROBEwatch.
>>    Moreover, we would like to know the location of the new Probewatch
>>    manual ( for the reporting use in particular -> msg :"nsrpt: No reports
>>    available for agent...") because TNPUBS::PUBLIC$DISK:<PUBLIC.ONEHUB>
>>    seems not to be correct.
See Note 1142.5 for report hints.
 | |||||