Conference azur::mcc

    
    
    
    	An alternate location in Europe for the MIB definitions is
    	TENERE::EMA$PUBLIC:[MIB].
    
    
    		
                Hope it helps...
    
    
    			CjH

	Note that some of the mibs will translate properly only with the
	latest mib translator on the X1.2.18 base level kit. The old translator
	could not handle mib extensions in the standard branch of the internet
	tree (i.e under mib-2). So if you need to add any of the standard
	mibs ( with *_STD_MIBDEF.TXT as file names), and if you are unwilling
	to wait for the next release, you can copy the latest mib translator
	from YAHEY::YAHEY_USER:[BOSE.PUBLIC]MCC_TCPIP_MTU.EXE.

	Rahul.

    I noticed that the Cisco mib has the three write-only variables
    included. Can the Iconic Map PM now handle write-only variables
    correctly?
    
    - Mike

	Mike,
		I don't remember your original problem with write-only
	variables using the iconic map. But I might mention that all
	write-only variables are modeled as read-write attributes, i.e 
	you can do both sets and shows on it. If an agent supports only
	writes to that particular variable, then you should get Attribute-
	Not-Gettable when you try to do a show on it.

		I don't know what particular problem you had with the iconic
	map regarding this attribute, but most probably the problem still 
	exists.

	Rahul.

	

    Rahul,	
    
    There is a subtle difference in the processing of a reply sent back
    by a request for a read on a write-only variable and a read on a
    non-existant variable.  I compiled your cisco mib which includes the
    write only variables and then executed a SHOW SNMP xxx cisco LSYSTEM
    via the iconic map pm ... this resulted in an 'Internal logic error
    26' message, with none of the Lsystem information being displayed. 
    Either the iconic map pm or the SNMP AM must be fixed to eliminate
    this problem. Otherwise you should consider modifying the Cisco mib
    included with the AM and comment out the write-only variables. It
    won't look good if the 'supported/tested' mibs shipped by DEC don't
    work.
    
    - Mike

	Mike,
		I did not know what the problem was. I agree that it needs
	to be fixed and a QAR has been filed against the SNMP AM.

	Rahul.

	A general comment about your statment, 

	"It won't look good if the 'supported/tested' mibs shipped by DEC don't
 	 work."

	We don't claim to support the mibs that are on are kit.  These mibs
	are provided by the vendors.  We included them on our kit as a
	convenience to our customers.  We are not in the business of sanitizing
	mibs and verifying that the mib accurately represents the agent
        implementation.  Customers need to be educated that they should be 
        leaning on these vendors when problems arise with a mib or agent.

Dan

    While mibs should not have the warrenty to work with the vendor's
    agent, they should be adjusted to MCC - to provide the workarounds for
    indexed attributes, includes from other mibs, and other things where
    MCC's compiler is different from standard compilers (mosy?)
    
    bill

    Does anyone have a copy of the latest Xyplex MIB?
    
    Will a Xyplex MIB be included in the V1.2 kit along with the other MIBs
    mentioned in .0  ???
    
    Thanks,
    Dan

	
	A xyplex mib will indeed be provided on the V1.2 kit. It should
	be in the X1.2.7 field test update kit. Send mail to Elias if you
	need it before that.

	rahul.

    Dan,,
    The xyplex MIB is at PA::DKB100:[PUBLIC]XYPLEX_MIBDEF.TXT
    
    regards...elias

    Rahul,
    
    I have X1.2.15 installed and it wasn't part of the kit.  You might
    check again to be sure that I'm not going nuts and that it gets in 
    X1.2.19 and thereafter.
    
    Thanks for the pointer, Elias.
    
    Dan  :^)

    Would someone please change the protection on the XYPLEX_MIBDEF.TXT
    file?
    
    -Thanks,
     Dan

	RE: .12

	Dan,
		You are right. We added the xyplex mib to the kit pretty
	late in the game. But I can assure you it is on X1.2.19 and subsequent
	kits.

	Rahul.

    I've recently installed T1.2.7.  The XYPLEX_MIBDEF.TXT file is not part
    of this kit.
    
    Will someone please change the protection on the file on node PA:: as
    mentioned earlier so that I may copy this file?
    
    Thanks,
    Dan

Dan,

	My investigation shows that the xyplex_mibdef.txt is on the T1.2.7 kit.


	Build system, saveset D directory for t1.2.7 base level...


Directory USER$772:[MCC_ROOT.BUILDS.T1_2_7.SAVESETD]

XYPLEX_MIBDEF.TXT;1
                       1088   2-APR-1992 17:37:22.00  (RWED,RWED,RWED,RE)

Total of 1 file, 1088 blocks.


	Our lab system running here in Merrimack...


Directory MOLAR_USERB:[MCC]

XYPLEX_MIBDEF.TXT;5
                       1088   2-APR-1992 17:37:22.00  (RWED,RWED,RWED,RE)

Total of 1 file, 1088 blocks.

Dan

And the ULTRIX kit inventory shows:

/usr/mcc/mcc_system/xyplex_mibdef.txt   none    MCRBMST127

    
    
    Hi,
    
    I'm looking for private mibs related to 3COM (ie BR3000, IB2000, ...)
    and HIRSCHMANN equipments.
    
    Does anybody know either an EASYnet pointer or the 3COM/HIRSCHMANN 
    INTERnet pointers to get those private mibs ?
    
    Regards,
    Renato
    

I can provide you an answer for 3Com - 3Com has no private MIB extensions.
3Com only supports standard MIBs and in the case of the IB2000, I think they
only support MIB I.  I'm not sure whether the BR3000 supports MIB II, but
at any rate, it does not have any private MIB support, and none is planned.

Mgc

    
    
    Hi Merlin, and thank you for your reply !
    
    Even no 3com private MIBs seem to be planned, have you any information
    (contact, pointers) about HIRSCHMANN private MIBs ?
    
    Furthermore, is there any EASYnet pointer about the INTERnet worldwide
    community related to UNIX environment and SNMP management ?
    
    Thanks in advance,
    Regards,
    Renato