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

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
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

2656.0. "traps supported by DS900EF and RFC implmented?" by SNOFS1::63496::CHIUANDREW () Mon Aug 21 1995 00:39

    HI,
    
    Just want to clarify the traps sent from DS900EF, according to notes
    2376, 1317, DS900EF supports standard BRIDGE mibs, FDDI mibs, but these
    MIBS do not tell the traps (specific) will be sent, does it imply the
    following:
    
    1) DS900EF only sends generic traps (link up, down, etc..)?
    2) DS900EF cannot report the bridge network topology status events
    (i.e. bridge port becomes learning/broken/forwarding...)?
    3) DS900EF will not send any enterprise specific traps?
    
    
    Customer planning to have reductant bridge links (FDDI as primary and
    Ethernet as backup), between two EFs (in DEChub900), since there is a
    loop (detect by IEEE 802.1d), then the Ethernet bridge on one of the
    EFs will be BLOCKED, it will be changed to FORWARDING if the FDDI link
    is down), customer would like to get traps from EF when:
    a) FDDI link is down (I think EF will send a trap because FDDI is just
    another interface as far as the DS900EF is concerned)
    b) status change of its ethernet port on one of the DS900EF (this I am
    not sure whether DS900EF (V1.5) will send it out?
    
    
    could someone clarify the above?
    
    PS: Could someone advise the RFC numbers (bridge/FDDI) currently
    implmented by DS900EF.
    
    
    thanks in advance for help/idea/hints!
    
    
    Andrew Chiu -  Network services Sydney 
T.RTitleUserPersonal
Name
DateLines
2656.1RFC'sNETCAD::CURRIERMon Aug 21 1995 12:565
    Bridge   RFC1493
    
    FDDI     RFC1512