Conference netcad::hub_mgnt

744.0. "DECagent T2.0.10 problems and questions" by CGOS01::DMARLOWE (dsk dsk dsk (tsk tsk tsk)) Fri Feb 18 1994 14:15

    I thought I'd start a new note for the DECagent 90 FT T2.0.10.
    
    I have found what seems to be a problem with HUBWATCH T2.5 and the
    initial SPECIFY AGENT window.  It wants to work only with a string
    of PUBLIC.  This now gets me back to the DECagent 90 and things
    that were taken away from the V1.1 code.
    
    Going into the console port gives you the nice menu.  Select 5 (Set
    Agent Read/Write Community) and you are allowed to only set that
    string.  But what happened to the READ/ONLY string.  Because of
    Windows T2.5 problems (see note 725.3) I now have to set the DECagent
    90 to PUBLIC so I can get to it from the initial window in HUBWATCH.

    It would be nice to be able to set the READ/ONLY string to PUBLIC
    and then something else for the READ/WRITE.  This way it wouldn't
    leave the DECagent quite so open and it would still work with Windows
    T2.5 and so on until Windows is fixed.  Why was setting the R/O
    string taken out?
    
    
    I don't know much about TCP addresses and subnet masks but why are
    you not able to set the subnet mask?  I have one customer saying
    that because they can't set the subnet mask then they won't be able
    to connect to any remote DECagent 90's.  Could there be a situation
    that because of the calculated subnet mask that they wouldn't be
    able to get to the agent over a WAN?
    
    
    Also I'm sorry to see that you can't add/delete communities or enable
    or disable ports other than those that are in the same hub as the
    agent.  I have found countless quirks with DECagent V1.0 and V1.1
    code that could only be corrected by going into the console port.
    

    As I move my DECagent 90 around a lot sometimes it has different
    communities in it including DEChub 900 communities and its a pain
    to have to go to HUBWATCH to clean them out rather than putting
    a terminal on the console port and just deleting them.

    
    dave

    See topic 628 for a discussion of subnet masks.
    

Dave,

Regarding your question about subnet masks, it is really very simple.  The
DECagent does not support setting the subnet mask.  What we have provided is a
means to help you get to another subnet.  It's called the default gateway.  If
an IP address is on our subnet (determined by applying the default subnet mask
based on the agent's IP address), we talk directly to it.  If it is not, we'll
send the packet to the default gateway so it can forward it to the right place. 
If the default gateway is not defined, you can't get there from here.

I'll leave the answering of your questions about the DECagent's console to those
who made the decisions that affected the functionality you mentioned.

Roger Gaudet
DECagent 90 development

    
    Thanks SLawrence and Roger.  That makes sense.
    
    As to missing/changed items in the menu I have sent this to Bill
    Seaver.
    
    
    Only need answers to HUBWATCH for WINDOWS and SPECIFY AGENT startup
    window problems??!!

    Regards,
    dave