Conference netcad::hub_mgnt

    
    On the same subject if you enter the Manage Table option under the
    Community menu you get to see the Read-Write string listed along with
    the Read-Only, surely this is kind of insecure in terms of people 
    learning what your Read-Only strings are and possibly then being able
    to then restart Hubwatch using the Read-Write string and then having
    the ability to effect the HUB and it's configured devices.
    
    Giles

    I have also noticed that when accessing a HUB using Read-Only the
    options RESET and FACTORY are still available for the Agent and Bridge
    on the HUB. I havent tried them for obvious reasons, but should they
    really be available to select ?
    
    Giles.

    Giles...
    
    What version of the DECagent 90 firmware do you have?  I have fixed the
    console code (in fairly recent version, maybe X1.68?) so that it always
    tries to display the read-only community string on the screen.  There
    should be only two cases in which the read-write string of the
    currently selected community is displayed in the console screen header:
    1) read-only and read-write strings are the same, and 2) the read-only
    string is null.  If you have X1.68 or later and you are seeing
    something different from the above I am very interested in hearing from
    you.
    
    Of course, you can always get the read-write community string by using
    the Show Community command.
    
    ...Roger...

    Roger,
    
    	The version on our four DECagents here is V1.0 so I guess it's time
    to find a later source and upgrade them.
    
    	Further to a previous entry I listed I have also noticed the
    following :-
    
    	One of our DECagents is managing three separate 8-slot Hubs
    and resides in one of them. If I fire up Hubwatch to one of the two
    Hub's without the Agent in, and select the Community option and Manage
    Table option, Hubwatch crashes. However If I fire it up selecting the
    Hub with the Agent in I can then select the option ok, and change my
    default community to one of the others and then switch back again ok.
    Any ideas ?
    
    	It appears that if you select the Manage Table option while being 
    Read-Only access you get to see all the Read_only and Read-Write
    strings for all the communities managed by the Agent. Surely these
    Read-Write strings should not be displayed as I questioned in a
    previous note, but should only be displayed if you fire up Hubwatch
    as Read-Write access. It also seems that you still use the APPLY
    option even if Read-Only access ?
    
    Giles.	
    

    Roger,
    
    	Appologies if this is already listed in this conference and I have
    missed it, can you point me in the direction of the latest DECagent
    source, and how do I upgrade them eg LOAD/TRIGGER equivalent ??!!
    
    Cheers,
    
    Giles.

    What version of HUBwatch are you running?

    The Version is T1.1.8. of Hubwatch
    
    Giles.

As of 12 February 1993, the following files are on the public directory
EMDS::MANAGEMENT:   To copy a file from this directory, type:
	COPY EMDS::MANAGEMENT: file_name
    
    for loading the DECagent
# AGENT_LOAD.TXT= How to load current micro-code on agent
    
    for pointer to latest agent code (1.7X)
#VMS_LAUNCH.TXT= how to load HUBwatch for OpenVMS 1.1

    I have copied over the file DENMAV1_0.EXE;1 and followed the
    instructions in the file AGENT_LOAD.TXT but get the following
    when trying to load one of my Agents from a 4000-300 running VMS.
    
    CCI> load denma.exe
    
    DENMA -901- Initializing DECagent 90.
    DENMA -953- Attempting to locate load host
    [ISO8802]
    DENMA -953- Attempting to locate load host
    [ETHERNET]
    DENMA -955- Host AA-00-04-00-64-A8 located [ETHERNET]
    DENMA -956- Requesting load from host AA-00-04-00-64-A8
    DENMA -903- Loading from host AA-00-04-00-64-A8
    DENMA -912- Load failure, timeout
    DENMA -953- Attempting to locate load host
    [ETHERNET]
    DENMA -955- Host AA-00-04-00-64-A8 located [ETHERNET]
    DENMA -956- Requesting load from host AA-00-04-00-64-A8
    DENMA -903- Loading from host AA-00-04-00-64-A8
    DENMA -916- Illegal load image, load aborted
                                                �
    %CCI-I-CRCCHK,attempting CRC check on image loaded
    
    CCI>
    
    Why is this failing ?
    
    Giles.
    

    Try the load again (and maybe again, and again, and...).  The CCI load
    procedure is not very tolerant of busy networks (it attempts to use
    1500-byte packets to load the file).
    
    The only alternative is to isolate the load host and DENMA from the
    network backbone and perform the load in that environment.
    
    ...Roger...

     I will do as you suggested ,
    
    	Cheers. 
    
    	Giles.

    After spending a fair amount of time getting one of our Agents upgraded
    with the source file DENMAV1_0.EXE I find that it's on version V1.0
    which is what were already running here. So where's a later source that
    will allow me to manage 90TL servers ? I did suspect that due to the
    above filename that it might be the same version but I thought that
    maybe even though it might be X1.** that the file was still called
    V1_0.
    
    Any pointers to the latest code, eg: like the location of the X1.68 
    version previously mentioned.
    
    	Giles.

    Look in VMS_LAUNCH.TXT.  There is a pointer ther to latest code. 
    Should be 1.72 or above....

    Thanks for pointer to the latest Agent software. I have upgraded one
    of the agents here to X1.74. However I notice that on connecting to
    the console port of the agent I get lots of spurious characters at the
    command prompt and at the top of the screen. 
    
    Also if I try and add a module I only get four options and cannot add a 
    Decserver 90TL which I have three to add. The options list overwrite
    the information on the screen and when entering the MAC address it
    seems to place the characters all over the top of the screen. Is this
    all known about or do I have to disabled something to stop this
    happening ?
    
    When firing up Hubwatch to this Agent i notice that the APPLY feature
    doesn't work at all now if READ-ONLY but you can still use FACTORY and
    RESET and see the read-write community strings, is this being changed
    in a future release or being left as is ?
    
    Giles.

    The DENMA will not, in any version, "manage" the DECserver 90TL. 
    HUBwatch V1.1, inconjunction with DENMA V1.1, will.  90TLs are
    auto-discoverable, so they are not manually added to the agent.  However,
    the 1Mb version of the 90TL must be added with DENMA polling disabled,
    as it will disappear from the hub after its image is loaded.
    
    Note that we appreciate your input about the latest X1.xx releases of
    DENMA, however remember that this is still experimental software and
    we're working on solidifying the code.
    
    FYI, DENMA X1.75 was released yesterday (Fri. 3/12).  This version
    should fix the strange characters you saw on the screen.
    
    ...Roger...