[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

1173.0. "Decserver90L++ in Dechub900" by PADNOM::PEYRACHE (Jean-Yves Peyrache Country Support Group France) Wed Jun 29 1994 08:58

  hello,

 as the new version of firmware (V5.4) is mandatory to manage Decserver90l++
 in DECHub900 with Decagent90 on it ???

  i have a Dechub900 in V3.0.0 with
  a Decserver90l V3.1
  a Decbridge90FL V3.1
  a Decagent90 V2.1.3
  a Decserver90l++ V5.2
  a Decrepeater900TM V1.0G.
  using hubwatch for Windows T2.0.1

  i have no trouble to manage a Older 90 series directly from the dechub900 view
  but for the Decserver90L++, if i "double-click" on it ,on the Hub900 view
  a error message appears "unable to communicate wiht the agent", in fact like
  a wrong community string problem.
  the same step works on 90l,90fl as well

  but all 90 series are in same community aka "public1" for me , and if select
  my Decagent90 in manage table of agent and goes to the community public1
  i can now manage my Decserver90l++???

  as anybody already manage successfully this version of Decserver90l++ in
  Dechub900 under Hub900 view ??

  thanks for any comments/request/pointers

  Jean-Yves
T.RTitleUserPersonal
Name		DateLines
1173.1Is it reachable from the DECagent console?ROGER::GAUDETBecause the Earth is 2/3 waterWed Jun 29 1994 10:248
The V5.2 code in the DECserver 90L++ should not make a difference.  Can you
check the DECagent console to see if the device is reachable (console menu 13,
then choose the community that the server is in)?  If it is reachable, you
should be able to get the server summary screen from HUBwatch.  I assume that
you are managing this hub in "90-style" (i.e. the MAM does not have an IP
address).

...Roger...
1173.2reachable of coursePADNOM::PEYRACHEJean-Yves Peyrache Country Support Group FranceWed Jun 29 1994 12:5213
  Roger,

  Module is reachable , i can access this module when i goes to the community
  of Decagent90.
  my problem is only under the Hub900 view , in fact i get first the error      
  message and just after a windows of DS90l++ but it/s generic windows
  with Hardware address equal 00-00-00-00-00-00.
  if i tried any change (disable port, port modification) i get another
  error message "snmp mib variable no implemented"

  any others comments ??

  jean-yves
1173.3DECserver 90L must be in agents fileSLINK::HOODI'd rather be at the KennebecWed Jun 29 1994 13:1518
Jean-Yves,

Is there an entry in your HUBwatch agents file for the DECserver 90L++?

The entry should contain:

IP Address:  The IP address of the DECagent 90
Agent name:  The name of the DECserver 90L++
Community:   The DECagent 90 community which contains the DECserver 90L++
Timeout/Retries:
MAC Address: The MAC address of the DECserver 90L++
Type:        Terminal Server

Without this record, HUBwatch cannot manage the DECserver <90L|90L+|90L++>,
nor the DECbridge <90|90FL>.

Tom Hood
HUBwatch
1173.4all seems good in setup of agentPADNOM::PEYRACHEJean-Yves Peyrache Country Support Group FranceWed Jun 29 1994 14:3213
  Tom,

 all parameters are already setted, and i have only the problem with the ds90l++
 no with 90fl or 90l.

  i know that's all kind of module talk mop, any known/unknown behavior
  with ds90l++, i thinks that hubwatch tried to talk directly with the ds90l++
  as like a snmp device.. funny no..

  thanks for any others comments

  Jean-Yves