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

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

495.0. "DEC VENDOR ELANEXT V2.0 MIB" by ZTOIS1::VISTA (Renato VISTA, SIS Strasbourg, France) Tue Mar 10 1992 06:19

    
    Hello,
    
    I'm working on an EMA/DECmcc V1.1 + SNMP V1.1 platform on VMS and I
    want to manage FDDI DECconcentrator 500 for an Onsite Customer
    Platform. 
    
    With the SNMP V1.1 kit, DEC_MIBDEF.TXT (ELANEXT V1.7) and FDDI_MIDDEF.TXT
    (Draft 0.7 nov.1990) are available and can be used with Firmware V3.0B
    of DECconcentrator 500 (SNMP GET requests ONLY).
    
    I've just received firmware V3.1 of DECconcentrator 500 (GET and SET
    requests allowed) and I've just read in the release notes that DEC
    VENDOR MIB ELANEXT V2.0 of Nov.1991 is necessary to manage FDDI
    entities via SNMP. I've tried to obtain information on node
    gatekeeper.dec.com (ie Internet NODE 16.1.0.2, DECnet NODE 10.429,
    via VALBONNE) throught ftp (anonymous account) BUT the /private/mib 
    directory is empty !!
    
    How can I obtain those information ?
    
    Thank you for your help !
    
    Renato VISTA
    
T.RTitleUserPersonal
Name
DateLines
495.1The MIBs are really there.QUIVER::HARVELLTue Mar 10 1992 09:5514
    The /private/mib directory is not empty but it is protected.  You
    cannot do a ls of it.
    
    Once you change directory to /private/mib do a get on the file README
    (remember to be case sensitive).  This file will list the names of all
    MIBs that are stored in the directory.  You can then get each file that
    you want.
    
    If you try and do a ls of the directory your connection will be
    terminated.
    
    And no I don't know why it was done this way...
    
    Scott
495.2OK for README but NOT for others MIBS filesZTOIS1::VISTARenato VISTA, SIS Strasbourg, FranceWed Mar 11 1992 06:0224
    
    
    Hello Scott,
    
    Thank you for help !
    
    I've effectivly been able to get the README file and I've tried to
    obtain the dec_elan_vendor_mib_v20.txt. BUT I've got the following
    messages :
    
    FTP>connect .gatekeeper.dec.com
    FTP>username anonymous / password anonymous
    
    FTP>set def "/private/mib"
    FTP>get dec_elan_vendor_mib_v20.txt
    200 PORT command successful
    550 DEC_ELAN_VENDOR_MIB_V20.TXT: Permission denied.
    
    For any files, the messages are the same.
    
    Have you got any idea to obtain those files ?
    
    Thank you for your help.
    Renato
495.3MIPSBX::thomasThe Code WarriorWed Mar 11 1992 07:343
Put the name in quotes.  Remember VMS upcases by default.

(or use the unix of UCX FTP).
495.4OK for ELANEXT MIBs !ZTOIS1::VISTARenato VISTA, SIS Strasbourg, FranceWed Mar 11 1992 08:246
    
    To .3...
    
    It's OK !
    Thank you for your help !!
    Renato
495.5FDDI MIB:expected 0.7 Nov.1990, found 0.6 Nov.1990#ZTOIS1::VISTARenato VISTA, SIS Strasbourg, FranceMon Mar 16 1992 09:1613
    
    
    Hello,
    
    Is it normal that in the FDDI MIB file, fddi_mib_nov_1990.txt (draft
    0.7 of November 1990) that I've got on gatekeeper.dec.com, the text
    written in the file itself describes the MIB as a version 0.6 (!!) of
    November 1990 ? Can that 0.6 version be integrated with DEC VENDOR ELANEXT
    V2.0 for SNMP management of DECconcentrator 500 (firmware V3.1) ?
    
    Thank you for your help !
    
    Renato
495.6LEVERS::ANILMon Mar 16 1992 20:1410
    The author of that draft neglected to update all the places where
    the version was referenced to 0.7, with the result you describe.
    This is partly why the filename refers to the date rather than
    the version.
    
    As far as your second question, ELANEXT is separate from the FDDI MIB.
    (DECconcentrator v3.1 manageability is described by the combination of
    MIB-II, draft FDDI MIB and DEC-ELAN-MIB)
    
    Anil
495.7OK for FDDI draft 0.7ZTOIS1::VISTARenato VISTA, SIS Strasbourg, FranceTue Mar 17 1992 03:0712
    
    
    Hi Anil,
    
    And thank you for your reply !
    
    So, I will rebuild parse-tables of DECmcc /VMS V1.1 with the two
    private mib files (ie dec_elan_vendor_mib_V20.txt and
    fdd_mib_nov_1990.txt) to manage DECconcentrator 500 V3.1.
    
    Regards,
    Renato
495.8Failure during translation of FDDI_MIB_NOV_1990ZTOIS1::VISTARenato VISTA, SIS Strasbourg, FranceTue Mar 17 1992 05:3241
    
    Hello,
    
    I've tried to translate the file DEC_ELAN_VENDOR_MIB_V20.TXT and
    FDDI_MIB_NOV_1990.TXT (draft 0.7) with MCC_TCPIP_MTU.COM command file of 
    TCPIP_AM V1.1 for DECmcc/VMS V1.1.
    
    For the DEC_ELAN_VENDOR_MIB_V20.TXT file, no problem.
    
    For the FDDI_MIB_NOV_1990.TXT file, after first update the ASN.1 source
    file because of a syntax problem (a comma was missing on line 1009),
    I've found the following error messages during the translating phase :
    
    ...
    Issuing following command :
      $ MTU "$ SYS$sSYSTEM:MCC_TCPIP_MTU.EXE"
      $ MTU SYS$COMMON:[MCC]FDDI_MIB_NOV_1990.TXT
      Table snmpFddiSMTTable does not have any associated index.
      Table snmpFddiMACTable does not have any associated index.
      Table snmpFddiPATHClassTable does not have any associated index.
      Table snmpFddiPATHConfigTable does not have any associated index.
      Undefined type FddiPathConfig
      An error occurred while running the MIB translator.
      Check file SYS$COMMON:[MCC]FDDI_MIB_NOV_1990.LIS for any further
      information.
      File SYS$COMMON:[MCC]FDDI_MIB_NOV_1990.MS may also have been created;
        delete this file as appropriate.
      
        17-MAR-1992 10:44:53
    
    Procedure terminated in error.
    
    ...
    
    Actually, I'm rebuilding the parse tables with the originate file of
    TCPIP AM V1.1 kit for DECmcc/VMS V1.1 (FDDI_MIBDEF.TXT file).
    
    Thank you for your help !
    
    Renato