[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

603.0. "DECagent90 can't detect 90L+ if DECbridge" by HGOVC::ALEXCHEUNG (Alex Cheung @hgo) Mon Jan 10 1994 23:21

Hi,

We have the following problem:
DECagent 90 could not detect 90L+ if DECbridge is installed on the same hub. 
This prevents HUBWATCH from managing the modules on the hub.

System Configuration	: DEC 4000 model 600 (OpenVMS/Axp V1.5)
                          DEChub 90, DECAgent 90
			  DECbridge 90, DECRepeater 90T, DECRepeater 90FL
                          DECserver 90L+

Layered Product &
Version/Patch applied	: MS Windows 3.1, Hubwatch for Windows V1.0


Problem Information	: 

  BACKGROUND:
  This client is using an DEC 4000/600 at the main site and has 2 other sites.
  PCs and VT420s are deployed on these 3 sites using DEChubs, repeaters, bridge,
  and terminal servers. We are installing HUBwatch for Windows V1.0 to manage
  the network. Each site have 2 DEChub 90s with repeaters and terminal servers.

  The first DECagent 90 that arrived is DOA - the agent's console port is not
  responding. So we 'borrowed' an agent from another client which was working.
  There are 2 hubs at the main site connected together with the following
  configuration:

            HUB #1                      HUB #2
  Slot 1 -  DECserver 90L+              DECserver 90L+
  Slot 2 -  DECserver 90L+              DECserver 90L+
  Slot 3 -  DECserver 90L+              DECserver 90L+
  Slot 6 -  DECrepeater 90T 
  Slot 7 -  DECrepeater 90FL
  Slot 8 -  DECbridge 90 FL             DECagent 90

  Problem:
  Using the console of the agent, we are unable to configure the agent with
  above setup. Everytime we configure the bridge, the 90L+s are lost - the agent
  would not recognize the servers. If the bridge is not configured, then all the
  other modules are recognized.

  This problem is thus carried over on the HUBwatch which requires the agent to 
  be properly configured.

o Action or test done so far and observation -
  We tried inserting the bridge on slot 8 of the second hub and the agent on
  slot 8 of the first hub with the same results. Using the first hub with the
  bridge on slot 8 and agent on slot 7 and vice versa did not work as well.


Does anyone have experince on such setup? Have we missed anything? Is the
configuuration fine?

Thanks for any advises.

best rgds,
alex
T.RTitleUserPersonal
Name
DateLines
603.1Works for me eith DECagent V1.1QUIVER::GAUDETTue Jan 11 1994 14:1342
    Alex,
    
    I am unable to reproduce your problem.  Given the description of your
    setup, I made the following assumptions:
    
    1) The network backbone is connected to HUB #1 (since you didn't
       specify, I'll guess it is through the bridge, but it really doesn't
       matter.)
    
    2) The hubs are networked together with a coax cable connected to each
       hub's BNC.
    
    3) The hubs are *NOT* connected together by a management cable.
       If they are, remember that HUB #2 is really slots 9-16 of a single
       16-slot DEChub 90 configuration.
    
    Using a DECagent 90 with V1.1 code and given the above assumptions, I
    did the following:
    
    - Put the DECagent into slot 8 of a DEChub 90.
    - From the agent's console:
      * Reset the agent to factory settings
      * Added the DECservers to slots 1-3 (community = 'public')
      * Created a second community (community = 'public2') and answered
        "NO" when asked if a bridge would be a member of this community.
      * Added the DECservers to slots 1-3
      * After about 20 seconds, the Show Community screen indicated that
        they were all there and communicating.
      * Added the DECbridge to slot 8
      * After about another 20 seconds, the Show Community screen indicated
        that the bridge and repeaters were available along the DECservers
        in their previously designated slots.
    
    Did I do something different from you?
    
    Also, it would be useful to know the versions of code you are running
    in your DECagent and DECbridge.  FYI, the latest is V1.1 and V3.1,
    respectively.
    
    Roger Gaudet
    DECagent 90 development
    
603.2QUIVER::SLAWRENCETue Jan 11 1994 14:171
    See note 530; it may be relevant
603.3tksHGOVC::ALEXCHEUNGAlex Cheung @hgoMon Jan 17 1994 02:115
    Roger,
    
    Thanks. We will upgrade the s/w and test as your procedures.
    
    best rgds