[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

953.0. "MIBs for a Repeater90C in an 900 backplane" by WELLIN::MCCALLUM () Tue May 03 1994 10:41

    
    What MIBs do I need to manage a DECrepeater 90c in a DEChub 900
    backplane ?
    
    I have tried the RFC1516 repeater mib, the DEChub900erptr mib and
    neither of these seems to see the module. Do I need the old DH90
    mib as is used fot a DECagent 90 ?
    
    I am trying to put an alarm on a port on a repeater from DECmcc, I can
    see the modules via the Chassis MIB but cant see into them.
    
    Thanks for any help,
    
    Dave McCallum
T.RTitleUserPersonal
Name		DateLines
953.1Trying community from ChasenetityWELLIN::MCCALLUMTue May 03 1994 12:3615
    
    I have been trying by using the backplanes IP address and the
    community name given when I do a show chasenttity chasentitycommunity
    for the module, this is a long string like %x7075623Dc63D3D and I think
    it is created dynamically - this is a DECrepeater90 I am trying to
    manage.
    
    I have been able to see ports on a DECrepeater 900 by using its own ip
    address so I have made some progress on one front.
    
    Thanks for your quick response - am I trying the right paths ?
    
    Thanks
    
    Dave McCallum
953.2Use RFCs and Digital ExtensionsLEVERS::PAGLIARORich Pagliaro, Hub Products GroupTue May 03 1994 12:5724
>>  What MIBs do I need to manage a DECrepeater 90c in a DEChub 900
>>  backplane ?
    
    When managing a DECrepeater 90C in a DEChub 900 via the hub's
    management agent module (MAM), the following MIBs are supported (and
    used by HUBwatch):
    
    	1. Repeater MIB (RFC 1516 which obsoletes RFC 1368): basic and
                                                             address
                                                             tracking groups
                                                             only.
    
    	2. Digital Extended Repeater MIB: basic and address database groups
                                          only.
    
    	3. MIB II: system group only
    
    How are you attempting to manage the DECrepeater 90C? That is, are you
    using the hub's IP address and appending the slot number to the
    community string (e.g. public-6)?
    
    Regards,
    
    Rich
953.3community-slotQUIVER::SLAWRENCETue May 03 1994 20:1011
    The preceding notes got crossed in editing, but I think I can clear up
    the confusion.
    
    The community string for a module to be managed using the IP address of
    the hub is the community of the hub with '-S' appended, where 'S' is
    the slot number.  So if the hub community is 'public' then the slot 1
    community is 'public-1'.
    
    It looks like MCC is showing you that community in a hex-encoded form,
    but you need to use the ascii.
953.4Works fineWELLIN::MCCALLUMWed May 04 1994 09:094
    
    Works fine with ascii - thanks
    
    Dave