[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

2593.0. "DECbrouter 90s with V10.X Code and Hub for Win 3.1" by NCMAIL::SCHEID () Mon Jul 31 1995 16:27

    I have a customer who is running a pair of DECbrouter 90s with v9.*
    Cisco code and they can be managed by HUBwatch for Windows 3.1 ... The 
    same customer is adding a pair of Brouter 90s with Cisco v10.* code ...
    but cannot get at them with Hubwatch for WIndows 3.1 ...   Does
    the customer need to run HUBwatch V4.1 to manage the version 10.* 
    DECbrouters...
    
    
    
T.RTitleUserPersonal
Name
DateLines
2593.1Apparent HUBwatch 3.1 problemFOUNDR::OUIMETTEEyes of the WorldTue Aug 01 1995 16:5328
              <<< NETCAD::USER$521:[NOTES$LIBRARY]DEWBR.NOTE;1 >>>
                         -< DECbrouter-90T2,-T2A,-T1 >-
================================================================================
Note 870.2                         SNMP AGENT                             2 of 2
FOUNDR::OUIMETTE "Eyes of the World"                 21 lines   1-AUG-1995 15:52
                             -< HUBwatch problem >-
--------------------------------------------------------------------------------
    	Kevin, Charlie,
    
    I just tried this with HUBwatch 3.1 and 4.0; bottom line is that 4.0
    HUBwatch works with 10.x, 3.1 does not work. On the LAN analyzer I can
    see an snmp response coming from the DECbrouter to the HUBwatch 3.1
    platform, but then HUBwatch sends no more PDU's. I'll decode the PDU's
    later, but at this point, it looks like a problem in HUBwatch 3.1.
    
    Also, I tried using an old version of MSU/snmp to query the DECbrouters
    for cisco-specific MIB variables; no problem, under either 9.14 or
    10.0; this leads me to suspect HUBwatch at this point. I'll update note
    2593 in the hubwatch notesfile (you should mention when you cross-post,
    FYI :^), and perhaps the HUBwatch folks will be able to comment what
    the specific problem might be with HUBwatch 3.1, or if there's a
    work-around other than 4.0...
    
    		regards,
    
    Chuck O.
    ESE Router Interop
    
2593.2May be sysOIDsNETCAD::FORINOWed Aug 02 1995 17:0510
    My guess is that the sysOIDs are different from v9.* to V10.* and this
    is what is causing the problem.  The HUBwatch code has a change in the
    sysOIDs for the brouters.  I'll try to get a confirmation on sysOID
    changes but the person who is the CISCO interface is out until next
    week.
    
    What platform are you running HUBwatch on?  I can confirm my guess if
    I can get an SNMP Trace.
    
    							John
2593.3Problem occurs under Hubwatch for Win 3.1NCMAIL::SCHEIDWed Aug 02 1995 22:227
    
    The customer is running under HUBwatch for Windows 3.1 ... They are not 
    planning to upgrade to v4.0 until later this year... unless they have
    to ...
    
    _charlie scheid
    
2593.4V4.0 OKNCMAIL::SCHEIDWed Aug 09 1995 22:124
    
    Upgraded all firmware and HUBwatch to V4.0 ... it works fine ...
    
    -charlie
2593.5MIB differencesFOUNDR::OUIMETTEEyes of the WorldWed Sep 06 1995 13:0337
    	John Forino's guess in .2 looks like it's correct; from the V10.0
    cisco MIB, note the modification beginning with 9,21 (which we never
    shipped for the DECbrouter- we went from 9.14 to 10.0).
    
              -- Product Section
    
              -- The product section contains the different product's
              -- object identifiers.  Each product has a unique object
              -- identifier allocated from this section which is referenced
              -- by the sysObjectID variable from RFC1156.
    
    
                   -- gateway-server      OBJECT IDENTIFIER ::= { products 1 }
                   -- terminal-server     OBJECT IDENTIFIER ::= { products 2 }
                   -- trouter             OBJECT IDENTIFIER ::= { products 3 }
                   -- protocol-translator OBJECT IDENTIFIER ::= { products 4 }
    
    >>>               -- Beginning with 9.21 sysObjectID returns platform
    			 based IDs
    
                   -- igs-sysID           OBJECT IDENTIFIER ::= { products 5 }
                   -- c3000-sysID         OBJECT IDENTIFIER ::= { products 6 }
                   -- c4000-sysID         OBJECT IDENTIFIER ::= { products 7 }
                   -- c7000-sysID         OBJECT IDENTIFIER ::= { products 8 }
                   -- cs-500-sysID        OBJECT IDENTIFIER ::= { products 9 }
                   -- c2000-sysID         OBJECT IDENTIFIER ::= { products 10 }
                   -- agsplus-sysID       OBJECT IDENTIFIER ::= { products 11 }
    
              -- New products will be added at the end of this list.
    
    
    	I'll let the HUBwatch folks indicate if any solution is likely with
    V3.1; my guess would be for slim chances.
    
    -Chuck O.
    DECbrouter Interop Engineering
    
2593.6ok so what to do?PRSSOS::HOFFMANNHOFFMANN Lionel/loc=evt/DTN number=858 5647Thu Sep 07 1995 07:065
    Interesting .So what do you suggest?
    modifying the mib?
    What about a future version of  hubwatch for openvms above 3.1?
    Thanks by advance
    Lionel 
2593.7SLINK::HOODMaine state bird: The black flyThu Sep 07 1995 11:481
There will be a HUBwatch for OpenVMS V4.1 in the not too distant future.
2593.8thank you PRSSOS::HOFFMANNHOFFMANN Lionel/loc=evt/DTN number=858 5647Thu Sep 07 1995 13:125
    thanks a lot for your reply
    do you know if it is possible to modify the MIB within HUBWATCH v3.1
    for doing the modifications.I can't believe but may be ......
    regards
    Lionel
2593.9SLINK::HOODMaine state bird: The black flyThu Sep 07 1995 18:501
No.
2593.10HUBwatch for OpenVMS V4.1 - on Alpha too?THEPUB::JRSJohn SHADE - &#039;Attila the Nun&#039;Tue Sep 12 1995 04:5710
RE: .7 >>There will be a HUBwatch for OpenVMS V4.1 in the not too distant future

I hope that this means OpenVMS Alpha as well as OpenVMS VAX! I know of several
customers who can't understand that we don't already offer HUBwatch on OpenVMS
Alpha.

While I'm on the subject, when will save/restore config to a file be
implemented? Surely it's just a SMOP - and funding... ;-)

-John
2593.11SLINK::HOODMy God, what have I done to my spleen?Tue Sep 12 1995 17:4616
>> I hope that this means OpenVMS Alpha as well as OpenVMS VAX! I know of

Can I assume you've been in personal contact with Jack NAC::Forrest, the
product manager?


>>While I'm on the subject, when will save/restore config to a file be
>>implemented? Surely it's just a SMOP - and funding... ;-)

Soon.  Very soon.  Check Bill Seaver's schedule, or ask Jack NAC::Forrest.

What is a SMOP?


Tom Hood
Backup & Restore (clearVISN Resilience) project leader.