[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

2745.0. "Revisit FDDI Ring Mapping Support" by HGRNCC::FARADAYCHONG () Wed Sep 13 1995 08:59

    Is FDDI Ring Mapping described in notes #1355.4/5 supported in
    HUBwatch V4.0?
    
    Faraday
            <<< NETCAD::KALI$USER3:[NOTES$LIBRARY]HUB_MGNT.NOTE;1 >>>
                   -< DEChub/HUBwatch/PROBEwatch CONFERENCE >-
================================================================================
Note 1355.4              FDDI ring map request from CERN                  4 of 7
NACAD::GALLAGHER                                     16 lines  29-AUG-1994 14:39
--------------------------------------------------------------------------------

I'm not sure I understand the question.  If you're questioning the difference
between an "SMT Gateway" and an "SMT/SNMP Proxy Agent" - there's very little
difference.

A HUBwatch application like FDDI ring map is invoked.  HUBwatch packages 
up an SMT frame, with the appropriate padding for source informations.  It 
then issues a set to the device, setting an object like, say, "smtGwRequest-
Frame".  The device takes the data (the SMT request frame), overwrites the 
source information with its source address, etc., and sends the frame.  
The device puts the response SMT frame(s) into "smtGwRespFrame".  HUBwatch 
reads "smtGwRespFrame", interprets the results, updates the map, and repeats 
until the ring configuration is known.  (Of course, other objects are involved
to provide synchronization, make the solution more generic, etc.)

							-Shawn
================================================================================
Note 1355.5              FDDI ring map request from CERN                  5 of 7
SLINK::HOOD "I'd rather be at the Kennebec"           5 lines  29-AUG-1994 14:50
                         -< DEChub - based FDDI maps! >-
--------------------------------------------------------------------------------
Sorry for the confusion.  The FDDI ring map that we hope will be in HUBwatch
V4.0 will require a DEChub-based ring.  GIGAswitch-based rings (without a
DEChub connection) will not be supported

Tom Hood
             
T.RTitleUserPersonal
Name
DateLines
2745.1NETCAD::B_CRONINWed Sep 13 1995 13:404
    
    No,
    
    There is no ringmapping function.
2745.2Hubwatch was not very useful...!!STKHLM::WEBJORNThu Sep 14 1995 07:2515
    
    This seems to be a problem in the eyes of the customer...
    
    MCS recently had a big problem at ABB, where some 30 servers, 2000
    clients dropped out periodicly. Due to the size and complexity of the
    installation, ( some 10 con's, 15 DS900's, all servers and routes on
    FDDI, 95 % DEC stuff, except HP servers ) they failed for days to
    trace out the problem.
    
    The helpful HP system manager ran a 'ring map hack' that provided 
    the ring info in ascii. Using that as a map the problems could be 
    identified. ( hw errors + subsequent misconfig )
    
    Gullik
    
2745.3The wish listSLINK::HOODMy God, what have I done to my spleen?Thu Sep 14 1995 23:0113
The FDDI Ring Map function for HUBwatch remains on the wish list, a prisoner
of too many other neat things to do.

The best way to increase the priority of a new feature is to contact our
beloved, knowledgeable, and ever-friendly HUBwatch product manager, Jack
NAC::Forrest.  And the best things to tell Jack about new features is how 
much new revenue they will produce.

Asking for features in this notesfile is not the same thing as contacting
product management.  Asking for them here only keeps them on the wish list.

Tom Hood
HUBwatch
2745.4Any non-HUBwatch solution?HGRNCC::FARADAYCHONGThu Sep 14 1995 23:3813
    FDDI Ring Mapping probably is better suited for SNMP application
    layered on top of generic SNMP manager. Unfortunately, there isn't one
    made by Digital run over Polycenter NetView.
    
    Is there one run over MS Windows or ManageWORKS? Appreciate any
    recommendation.
    
    At the least, can anyone advise hints and how-to roll-it-yourself on MS
    Windows or ManageWORKS? i.e., try to understand how easy to build an
    FDDI Ring Mapping application?
    
    Faraday
           
2745.5Touch ring, hubwatch/OSF 4.1 crashes.STKHLM::WEBJORNFri Sep 15 1995 12:147
    
    I guess the 'ring' symbol in the DS900 EF picture in hubwatch 4.1 OSF
    does NOT represent ringmap. In any case, touching that button crashes
    hubwatch.
    
    Gullik
    
2745.6apples & orangesNETCAD::CURRIERFri Sep 15 1995 12:448
    re .4
    
    This is true only if the fddi device supports gets to the SNMP fddi
    mib.
    
    To be compliant, all fddi devices must support and conform to SMT
    (ansi station management).  IP/UDP/SNMP is not the same as SMT.
    
2745.7Assume SNMP FDDI MIB support!HGRNCC::FARADAYCHONGFri Sep 15 1995 13:246
    re .6
    
    Yes, I failed to mention the assumption of SNMP FDDI MIB, didn't
    Digital made FDDI product support gets to SNMP FDDI MIB?
    
    Faraday
2745.8NETCAD::B_CRONINFri Sep 15 1995 15:2523
    
    The algorithm to build the logical ring mapper is fairly simple. 
    
    1) You start at station 1, and get its MAC address.
    
    2) You ask the station who its upstream neighbor is, either with SNMP
    frames, or, SMT frames. 
    
    3) You then repeat step 2 as many times as necessary until you
       find the station whose upstream neighbor is station 1. At that
       point you've got the entire ring map.
    
    You can add enhancements from there for detecting changes in the map,
    or also building a physical view of the ring (elms did a physical 
    ringmap using an RBMS to SMT frame gateway). 
    
    You can also build a map by watching NIF farmes and pairing up the 
    requests and responses.
    
    Like Tom said, there's too many things to do, and this falls off the
    list unless significant money can be attached to it. 
    
    
2745.9SNMP implicationsNETCAD::CURRIERFri Sep 15 1995 16:0010
    The difficulty with building a ring map with SNMP is that you must 
    use IP (therefore know the IP address of each device) to perform the
    SNMP get of each device's HW address, upstream nbr, & downstream nbr.
    You must do this for each device in the FDDI ring - not just for each
    device in a hub (assuming that the ring extends beyond the hub)
    
    i.e. each device must have an IP address & you must know this IP
    address.
    
    
2745.10re: crash in .5SLINK::HOODMy God, what have I done to my spleen?Fri Sep 15 1995 18:0114
>    I guess the 'ring' symbol in the DS900 EF picture in hubwatch 4.1 OSF
>    does NOT represent ringmap. In any case, touching that button crashes
>    hubwatch.
 

Gullik,

No, that button gets the FDDI info for the switch.
Have you reported the crash?


Tom Hood
HUBwatch   
 
2745.11colormap allocation problems ?????STKHLM::WEBJORNMon Sep 18 1995 09:366
    
    Apearently hubwatch interacts badly with other applications like
    netscape and mosaic. killing them, hubwatch works ok.
    
    gullik
    
2745.12SLINK::HOODMy God, what have I done to my spleen?Mon Sep 18 1995 16:282
Hmm, on my Alpha workstation, I just get bizarre colors when running Netscape
and trying to bring up HUBwatch.