Conference netcad::hub_mgnt

 hello,

>>>    When changing a e.g. IP address in the Community table from a
>>>    already configured module in the Community table and click on OK,
>>>    then the agent type will be 'OTHER' instead of the type that the
>>>    module already was before. e.g. FDDI concentrator.
>>>    Is this normal?   



   try this

  in Community table windows:

   1/select the Agent   
   2/click on Agent Options (in the right of the windows)
   3/Agent Options windows appears
   4/Modify Ip address in this windows
   5/click on OK (bottom of Agent Options Windows)
  
   it's work for me

   Jean-Yves

 >>. When selecting a DECconcentrator 900MX from the Hubwatch window it
 >>  used the community public. The complete HUB900 has a other community
 >>  than public. The Station Configuration shows the right configuration!
 >>   But when I (the customer) selected the DECconcentrator 900MX via the
 >>   Community table and maked them current then the DECconcentrator 900MX
 >>   used the right community but don't shows the right configuration in 
 >>   the Station Configuration window anymore! Is this a known problem or
 >>   do I something wrong?
 >>   The version of HUBwatch is 3.0 and the DECconcentrator 900MX firmware
 >>   is V2.0 .


  can you post items referring your Hub900 in Hubwatch_agents.dat file
  can you post display of  "Show Current Settings" on console options
  for DECcontrator900MX

  Jean-Yves

    
    Jean-Yves thanks for the response,
    
    reply on 1336.1
    >>  in Community table windows:
    
    >>   1/select the Agent
    >>   2/click on Agent Options (in the right of the windows)
    >>   3/Agent Options windows appears
    >>   4/Modify Ip address in this windows
    >>   5/click on OK (bottom of Agent Options Windows)
    
    >>   it's work for me
       
    That is working but if you then click on the Apply or OK push button
    on the Community Table window to execute the change (to save it) then
    the agent type will change to 'OTHER'.
    
     
    reply on 1336.2
    
    Extract off the HUBWATCH_AGENTS.DAT file;
    
    145.42.185.11 tnhuba "tnhuba" 5 2 AGENT900 #
    145.42.185.13 tnhubar3 "tnhuba" 5 2 REPEATER #DECrptr 900TM
    145.42.185.12 tnhubas4 "tnhuba" 5 2 TERMSERV #DS900TM
    145.42.185.14 tnhubar2 "tnhuba" 5 2 REPEATER #
    145.42.180.17 tnhubac5 "tnhuba" 5 2 FDDICONC #
    145.42.180.18 tnhubac6 "tnhuba" 5 2 FDDICONC #
    145.42.180.19 tnhubac7 "tnhuba" 5 2 FDDICONC #
    
    
    Current settings DECconcentrator;
    
    DECconcen 900MX - slot 5
    ==============================================================================
    
    DECconcen 900MX, 6 Port FDDI Concentrator, HW=v1,RO=v1.0,SW=V2.0.0
    SysUpTime                                 : 7 days 22:32:27   11 resets
    SNMP Read/Write Community                 : tnhuba
    SNMP Trap Addresses                       : Not Configured
    Status of Last Downline Upgrade           : TFTP Write
                                                00:04:38   10 resets
                                                Transfer Complete.
    In-Band Interface Hardware Address        : 08-00-2B-A4-38-0C
    In-Band Interface IP Address              : 145.42.180.17
    In-Band Interface Default Gateway Address : 145.42.180.1
    SNMP Port Traps                           : Disabled
      
    Ronald de Groot

  for the point 2 
  Ok i see it,


   it's documented in release notes of HUBwatch V3.0 page 12

  " in the Manage Table window (agent table) ,if any files (except agent type)
    in an agent entry is modified and "OK"or "Apply" is pressed.the Agent type
    changes to "Other".
    
   The Workarounf is to change the entry,press Apply ,then change the Agent Type
   to the correct value and press Apply again"

   Jean-Yves
 
  

    Jean-Yves,
    
    I read the release notes but not good enough! Sorry for that.
    
    Ronald

  for the point 1 and just for clarify:
 
  why are you added the  900MX in Agent table ??
  i think, you can only manage the 900MX from the Hub central view 
  tried to start Hubwatch wiht Ip address of 900MX instead ip address to HUb900
  to see if you have the same problem..

  i take one hour to reproduced your problem/config in my office

  Jean-Yves 

re .6:
You can (if you want) add the 900MX concentrator to the agents file, but it
is not necessary.  The only advantage of doing so is that it somewhat 
eases the stand-alone mgmt of the concentrator in that you can specify the
name of the concentrator on the command line (watch/agent myconc) instead of
its IP address (watch/agent <ip_of_conc>).

If you have 900-series modules in a DEChub 900 backplane, the only 900 module
you need to have in your agents file is terminal servers.  You can add the 
others if you want, but it doesn't really buy you much.  [you DO need to 
have 90-series bridges, DENMAs, 90-series terminal servers, etc, in you agents
file, but you don't need 900 series modules.]

Also, the "type" field in the agents file is for user documentation ONLY.  
It is NOT used by HUBwatch.  It is only there so that a user can glance through
the agents file and know what kind of device "myconc" is.

Tom Hood
HUBwatch

  yes my Hubwatch guru's
   
    
  only advantage in for a stand-alone config not in hub900
  
  but, if the 900MX is in the HUb900
  any restriction should be applied ??

  restriction like :

    _same community for HUB manager and 900MX or others undocumented "features" 
  


  Jean-Yves
  
  

No.  No restrictions.  (except terminal servers)  No undocumented features.

You can give it any community you want.

At that point, you're using the concentrator's agent ip/comm, instead of the
mam's ip/comm.

The *only* advantage I can think of for managing a module standalone instead
of through the hub is that it's faster to initially bring up a single module
than a hub full of modules, and some of the snmp will be a little faster.

Tom Hood
HUBwatch

>>No.  No restrictions.  (except terminal servers) 

 leave with v1.4 of NAS
  thanks for your explain

 Jean-Yves

 ps: can you explain ""I'd rather be at the Kennebec""

> leave with v1.4 of NAS

Something in the terminal server notesfile in the past couple of weeks leads
me to doubt this.  But I don't remember exactly what.


> ps: can you explain ""I'd rather be at the Kennebec""

Some things just can't be explained. :-) (The Kennebec is a river in north-
eastern Maine rising out of Moosehead Lake.  The top 6 miles of it is
whitewater;  great kayaking.)

Tom Hood
HUBwatch

        <<< TOOK::WORK$40:[NOTES$LIBRARY]TERMINAL_SERVERS.NOTE;32767 >>>
                             -< Terminal Servers >-
================================================================================
Note 1820.6                 NAS and Community String.                     6 of 6
TOOK::D_NELSON "Dave Nelson LKG1-3/A11 226-5358"     13 lines  29-AUG-1994 11:15
                         -< Schedule misalignment... >-
--------------------------------------------------------------------------------
    RE: .5
    
    The status is that it still doesn't work.  The necessary changes were
    ready late in the DNAS V1.4 development cycle, but because of
    insufficient time for regression testing in the DEChub 900 MAM and 
    Hubwatch schedules, we left it out of V1.4.  It could be added to a
    "patch" release, pending the necessary testing.  No specific pans are
    in place for this, yet.
    
    Regards,
    
    Dave