[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

3025.0. "Can't connect lan groups to channels" by KAOFS::S_HYNDMAN (Zoom Splat Pilot) Fri Dec 01 1995 16:51

    
    
    
    	I have two dechub 900 populated with Portswitch 900FP's and
    Portswitch 900TM's.  In each hub I have create lan segments.  In each of 
    the portswitch modules I have created lan groups and assigned ports to 
    these lan groups.  I am now trying to connect the lan groups in the 
    portswitches to the lan segments in the hubs. I receive the following 
    error;
    
    	unable to communicate with agent...
    
    	unable to complete check for possible repeater loop if current 
    	operation is completed
    
    	aborting current operation
    
    	I receive this error message from Hubwatch for windows V4.1.1 and
    Hubwatch for Digital Unix V4.0.1.  This error message is received
    regardless of which hub/portswitch/lan group I am trying to connect.
    
    	The Hubs are running V4.0.0 of the firmware.  The portswitch 900TP are
    V2.0.1.  The portswitch 900fp are V1.1.1
    
        I logged a call with the CSC and they said they were able to connect 
    lan groups using Hubwatch for windows V4.0.1.  I asked them to upgrade
    and see if it breaks but I haven't heard back.
    
    	This network is dead in the water since I can't connect anything
    togther.  Portswitch modules seemed like such a good idea when reading
    the buyers guide.
    
    	What's not working here? Hubwatch,portswitches,hubs???
T.RTitleUserPersonal
Name		DateLines
3025.1Things to check:SLINK::HOODMy God, what have I done to my spleen?Fri Dec 01 1995 17:076
You might have connectivity problems in your configuration.

Double-check that you've got connectivity between your workstation and the
IP services module.  Does that connectivity exist in the configuration you're
trying to set up?
3025.2Are you connected?LEMAN::PAIVAHawkeye - Network Support @GEOMon Dec 04 1995 04:345
    As Tom said in .1, make sure the MAC address of the module you're
    trying to access is connected to the same LAN engine that you use to
    access the module from your HUBwatch PC.
    
    Pedro
3025.3Drop back and punt..ALBANY::BARTLEYMon Dec 04 1995 09:0415
    I experienced the same thing while setting up somes hubs for a 
    customer. This was just a couple of weeks ago, brand new hubs (5 of
    them), PS900FP & PS900TP in each. I think the MAMs were at V4.0.1 and
    HUBwatch was at V4.1.1. I had the latest firmware, so I upgraded the
    hubs that were online. I then tried to connect the FP & TP to lan
    segments and got the same errors as the base note. There were two hubs
    that didn't give me any problems, and they were the ones that didn't
    get upgraded. Burned up a lot of hours trying different things,
    including the repeater loop don't care button.
    
    I got a copy of old MAM firmware (V3.1) off the net and downgraded the
    MAMs, which didn't work too good w/HW4.1.2, then upgraded to the
    current version, and everything worked fine after that.
    
    Dave
3025.4anything else I can check?KAOFS::S_HYNDMANZoom Splat PilotMon Dec 04 1995 09:3213
    
    
    I have my pc connected into port 1 of a portswitch 900TP.  This module
    has one lan group.  The mac is part of this lan group.  This TP is also
    the ip services module for the hub.  I have no problem looking at and
    manipulating anything in the hub.
    
    I tried turning off the loop detection as mentioned in .3 but that
    didn't work either.  
    
    Still broke....
    
    Scott
3025.5KAOFS::S_HYNDMANZoom Splat PilotTue Dec 05 1995 10:5023
    
    	Over the screams of users clamoring for application access, with
    total disregard for availability requirements and change management 
    procedures, empowered with a mouse and Hubwatch/Hubloader I upgraded the
    firmware in everything that didn't move.  I was then able to connect
    the existing lan groups from the portswitch modules to the lan segments
    in the hub Hooorah!.  While I was n.1.0 off on my previous firmware 
    versions, they appear to be significantly different ie. didn't work.
    
    	Unfortunately I had a new problem that I couldn't name the lan
    groups in new portswitches and assign ports to those groups.  So I
    burned some incense and clicked all the buttons in Hubwatch, removed and
    inserted modules and general farted about until it suddenly decided to
    work.  Weird.
    
    	I am now a happy camper but I'm left with the feeling that we need
    some sort of debugging capability in Hubwatch.  The ease of use of
    Hubwatch is great, but what can you do to determine the problem when
    the ligos won't stick or you get popup error messages that can't
    identify the problem.
    
    Scott