[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

4414.0. "hub community string not settable" by PTOJJD::DANZAK () Thu May 15 1997 03:30

    I just upgraded a hub from V4.0(mumble) to V5.1
    
    I can NOT change the hub community string from PUBLIC?????!
    
    
    HELP!  All the firwmware is at the rigth version (i.e. urrent) etc.
    I power cycled teh hub, rebooted it, took
    away the IP characteristics, tried to reset it, etc
    
    
    Any thoughts?
    
    Thanks,,we really want to secure this hub and...aarugh..
    j
T.RTitleUserPersonal
Name		DateLines
4414.1More detail please.NETCAD::GALLAGHERThu May 15 1997 14:0421
Jon,

Can you supply a little more detail?

Which community string(s) do you want to change, the read-only, read-write,
or both?  How do you know you can't change community strings?

In an effort to predict what the problem might be....you can change the
read-write community via the Management Agent Module's setup port/console.
You can not change the read-only community string.  So if you're changing
the read-write community string and access the hub using the "public"
community string you should expect to be able to read all about the device,
but be unable to change the device's configuration.  

You can not block all SNMP access to the device by changing the read-write
community.  In order to do this you must change both the read-only and
read-write communities.  (Oh, and [blush] you can't change the read-only 
community using anything we produce.  You must use something else to set 
"pcomSnmpAuthReadOnlyCommunity".)

						-Shawn
4414.2Jon's not crazyNETCAD::MILLBRANDTanswer mamThu May 15 1997 14:2316
There is an actual upgrade bug here, just discovered.
The read/write community in not correctly converted 
from the storage format used in V4.x and earlier to the
format in V5.x.  It ends up being still readable, and
the console setup operation to change it reports success,
but the community for the hub is not changed.  (Curiously,
the community for a module when accessed through the MAM,
such as mumble-4 for the module in slot 4, does change,
but without the hub change it buys you nothing.)

This will be fixed in the upcoming V5.2.  Til then,
advise customers to change the community back to public
before upgrading.  Once upgraded, you must either stick
with what you've got, or reset to factory defaults.

	Dotsie
4414.3clarificationNETCAD::MILLBRANDTanswer mamThu May 15 1997 14:2510
I should have said 

Til V5.2 is available,
advise customers to change the community back to public
before upgrading.  If you have upgraded with a non-default
community (ie not public), then you must either stick
with what you've got, or reset to factory defaults before
you can change it.

	Dotsie
4414.4It's a bugPTOJJD::DANZAKFri May 16 1997 13:4419
    RE: .-1
    
    It's the HUB community (you know, the ONLy one that you can chance from
    the console without redirecting..
    
    The bug that dotsie indicated is the hub......aarugh.
    
    Oh well....
    sigh
    
    Yes, changing ALL the community info from the console (or something
    that we product) would be nice....
    
    "Digital, you always do a great job but never FINISH it!..."
    
    We need to finish more things before going onto great and wunnerful
    stuff.
    j