Conference netcad::hub_mgnt

2246.0. "Probewatch and TEC RMONplus pod" by HEN::SCHNEIDER (Rick Schneider (315)461-9938) Tue May 02 1995 13:19

	After further investigation of the problem with using a TEC RMONplus
probe with PROBEwatch 3.2.0. I needed to ensure that I used the level2
community name as the "read-only" community name (default is rmon).

	The write community name should use a level3 community (default being
rmon_admin). 

	So the problem with the test using a Frontier specific mib variable for
write still looks valid.

	I'm also seeing a problem where I can add a domain for the TEC probe
and see it update the statistics in the Domain manager window. But when I do a
rediscover the domain just added disappears (OSF v3.2.2) and PC version 3.2.0.

	Below is the extract of the HP mib explaining the levels of community
names.. used by HP, TEC and AXON.

                                                                          
					regards,

					rick 


    -- The level of access right that maps to a community string.
    -- There are four levels with increasing degree of authorization.
    -- Each higher level is granted the rights of the lower levels
    -- in addition to the following specific privileges:
    --
    -- level1 - Read access to MIB-II objects.
    --
    -- level2 - Read access to MIB-II, RMON MIB, and LanProbe MIB
    --    objects, excluding the objects in the AccessControl group
    --    and in the captureBufferTable.
    --
    -- level3 - Write access to RMON MIB and LanProbe MIB objects, 
    --    excluding the objects in the probeAdmin, interface,
    --    and accessControl groups.  Read access to MIB-II, RMON MIB 
    --    (including the captureBufferTable), and LanProbe MIB objects 
    --    excluding those in the accessControl group.
    --
    -- level4 - Read and write access to all MIB-II, RMON MIB, and LanProbe
    --    MIB objects.