Conference azur::mcc

	The Proteon private MIB is not included on the SNMP V1.1 kit.

	You don't need the Proteon private MIB to "talk" to a Proteon box.
	Proteon devices support at least MIB I.

	Are you saying you can do

	UCX> loop P4100

	but can't do 

	MCC> register snmp P4100?

    RE:.1
    
    Exactly.....I can do a successful LOOP in UCX and it shows that P4100
    is alive.
    
    But the MCC> REGISTER SNMP P4100      fails with "no response from
    entity".
    
    I can TELNET to the 4100 also...
    
    Must something else be done to the Proteon unit before it will accept
    SNMP commands?
    
    Al
    

Thanks for the additional info, but I don't know what you mean by COMMUNITY.

Is this a TCP/IP term or an MCC term.  I could not find the parameter
COMMUNITY associated with an MCC entity.

Puzzled!
Al

Ok.....seems that I need to talk with Proteon.

I've been able to get into the console and see that there is a PUBLIC 
community, but it still won't respond to MCC.

Al

>I've been able to get into the console and see that there is a PUBLIC 
>community, but it still won't respond to MCC.

	Al,  is it really "PUBLIC", or "public"?  The default community name
	used by the AM used to be lower case.  If the Proten box is 
	configured to upper case you can either change it, or issue a command
	overiding the default, such as

		MCC> show snmp ____ whatever, by password "public"

	SNMP community names and the AM's qualifiers are discussed in the
	section on access control in the AM use guide.

	Mike

Mike,

thanks for the info......it really is "public"....need to watch my case
when in SNMP I guess.

Did read the section you referenced in the manual and it was informative,
but no combination of ,by password "public", seems to help.

I spoke with Proteon and they are also baffled.....according to them,
everything is set up properly.

If anyone has done this before and wouldn't mind a phone call I'd really
appreciate the help....unfortunately the P4100 is just a loaner and
will be leaving in the next day or two.

thanks for all input.
al

thanks very much for the calls from MCC engineering......

Don't quite know why but the Proteon box seems to need a reboot any time
any parameters are changed

After rebooting, I was able to register and talk to it from MCC.

Again thanks,

Al

    By the way, the need to reboot devices that are SNMP manageble after
    parameter changes seems to be common. Lots of people get bit by it.
    
    My advise is to be sure and plan plenty of time to set up register
    the first one of each type of device, then plan to make the needed
    changes to all the rest, then proceed.
    
    In some cases in a production network you may have to wait overnight
    or perhaps the weekend or longer before they can schedule the reboot
    so when setting expectations with the customer for installing and
    configuring DECmcc with SNMP, take this into account.
    
    Actually, this kind of thing is becomming common for DECnet now too
    since VMS V5.4 changed security to not have default NML access.
    At least you don't have to reboot the VMS system to fix it, but
    you do have to convince the system manager to do it. Plan for this
    too when setting expectations.
    
    s/rob

    Does anyone know if the PROTEON private MIB extensions are available on 
    the net. We have a demo of DECmcc managing some CNX 500's and would like 
    to use the extra mib information.
                     
    Cheers,
    Louis

re .10

    Contact Elias Hatem (TOOK::E_HATEM).   Elias is the SVP engineer who
    coordinates the 3rd SNMP MIB collection we do...  If we have a MIB from
    Proteon, he would know where it is.

    /doug

I got the original MIB from Elias.  It was dated Mar 91.  

When the problem began occuring, I contacted Proteon for help in resolution,
they thought that it was probably an incompatibility issue between the SNMP
 agent on the router, and the MIB extension loaded into the management system,
that's why they sent me the latest and greatest MIB extension in ASN.1 format.

So, my question still stands... How do we resolve situations like this from
a customer perspective without the percieved finger pointing?

Mgc

    Welcome to the world of (alleged) standards.  :^/

    As long as there is any room for interpretation, there will be
    MISinterpretation and interoperability problems.  (Hell, they'll be
    there no matter what.) There is currently no easy _technical_ solution
    to your problem and neither is there an easy administrative solution.  

    It is one thing to provide a "clearinghouse" service for MIBs (which we
    don't really do yet, but may end up doing) and quite another to act as
    a 'virtual CMS library' for every SNMP vendors agent changes... Unless
    a vendor is somehow legally and contractually bound to keep Digital
    abreast of ALL changes to their SNMP agents and MIB specifications,
    there is no way in hell (or in Littleton MA for that matter) that we
    can provide the 'one-stop shopping' that you and your customer so
    dearly want.  Sorry.

    Unfortunately, the only thing you can do to resolve this kind of
    situation is to work with (and work ON) the vendors supplying MIBs and
    agents to your customer.  I know this is not the *neat* solution you
    are hoping for, but as I said, there is no contract/agreement ANYWHERE
    with ANYONE that binds SNMP vendors to apprise Digital of MIB or agent
    enhancements.  So, until such mechanisms are established, working
    directly (and likely, constantly) with the SNMP Agent suppliers your
    customer is using is the only way you're going to avoid the "perceived
    finger pointing."

regards, 
/doug

    Louis,
    
    the rpoeton mib is located at PA::dkb100:[public]proteon_mibdef.txt,
    and a description file as well proteon_mibdef_description.txt 
    hope this help....elias
    
    

    Elias the description file is not there.
    
    thx, Stan

    I was told by Proteon that they have given us their MIBs, as I now
    see in previous replies.

    Does this imply that we are going to include them in MCC?

    If not, how does a customer get them to include them in MCC?
    
    dmm

	The proteon mib is shipped with the DECmcc V1.2 kit. You can find 
	it in MCC_SYSTEM after installation (/usr/mcc/mcc_system on Ultrix).

	Rahul.

    re. .17
    
    And under VMS??
    
    dmm

In MCC_SYSTEM:, just like he said...

>	it in MCC_SYSTEM after installation (/usr/mcc/mcc_system on Ultrix).