[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

3377.0. "Big Time problems here..." by DECWET::WHITE (Surfin' with the Alien) Tue Mar 19 1996 15:58

Something is seriously wrong...

Our site, ZSO, (DECwest) recently purchased two DEChub 900's,
brand new.

Nice piece of equipment and everything...but we have a bunch 
of DECbrouter 90T1's that show up on both DEChub's as 90T2's.

I have spent about a week and a half wrestling with TFTP (boy, 
what a joy) to get everything upgraded to the latest and greatest
firmware...but that does not seem to make a difference. On both hubs, 
these brouter T1's still get reported as T2's by both the LED's 
and hubwatch.

(I'm still looking for a 4.1.1.bin for the DEChub 900 however
...pointer please?)

Now, seeing how we bought this stuff brand new...isn't this 
a problem?

In fact, I can't ping any 90 series modules on the HUB I'm 
working on.

My questions are:

Am I not doing something write with my backplane?  It's my understanding 
that the brouter and a DECagent 90 (another module I can't talk to) are 
automatically attached to an internal segment on the backplane...as long as 
I have them inserted in the hub, and the hub is attached to my network, and 
the modules are configured with IP addresses, I should be able to ping them,
right?  I mean if I take the brouter out of the hub and run it standalone
I can ping it just fine.

Hubloader does not work either...I get SNMP set errors...I have to load modules
with the console...which does work.  But I get 'unable to determine brouter
type' errors and SNMP timout errors in hubwatch, and I can't ping any 90
series modules

This stuff is brand new??

What gives??

Should I be calling field service?

*Please* help...we've been at this for two solid weeks now and it's getting
way frustrating...

thanks in advance.

Stephen White
DECwest Engineering
T.RTitleUserPersonal
Name		DateLines
3377.1config vs software bugs.SLINK::HOODYour bad news bearTue Mar 19 1996 17:0910
Is there any connection between the segment on which your pc/workstation is
located and the ThinWire segment in the hub?  (If you are on one of the flex
channel Ethernets, is there a bridge or repeater between it and the ThinWire?)

Do you have IP running on the ethernet port of the brouter?
Do you have SNMP enabled on the brouter?
Did you add the brouter to the HUBwatch agents file?

Tom Hood
clearVISN
3377.2NETCAD::DOODYMichael DoodyTue Mar 19 1996 17:4535
>(I'm still looking for a 4.1.1.bin for the DEChub 900 however
>...pointer please?)
	As always, look in note #2.  Note 2.last announces the latest
    	kits that were released. Here is an internal Web pointer:
    http://npbww2.hpn.lkg.dec.com:80/npb/dr/hubs/firmware/dmhub411.bin

    Put http://npbww2.hpn.lkg.dec.com/ in your hotlist!



>In fact, I can't ping any 90 series modules on the HUB I'm 
>working on.

    	This sounds like you haven't connected your network to the ThinWire
    	segment in the hub. You should see the Brouter's traffic LED "->"
    	blink intermittently I think.

>My questions are:

>Am I not doing something write with my backplane?  It's my understanding 
>that the brouter and a DECagent 90 (another module I can't talk to) are 
>automatically attached to an internal segment on the backplane...as long as 
    	That's right, they are connected to the ThinWire segment 
        (colored Blue on the Hubwatch Lan Interconnect screen).


>Should I be calling field service?
>
>*Please* help...we've been at this for two solid weeks now and it's getting
>way frustrating...

	We try, but we're just volunteers helping the best we can.
    	If you need real help, you need to call real help people.

    -Mike
3377.3Thanks for the quick response!!DECWET::WHITESurfin' with the AlienTue Mar 19 1996 18:0122
Yeah, I got a sequence number open at CS...he said he
wants us to leverage this place as much as possible...

I really appreciate the help, starting to feel the pressure
*nervous grin*

OK, so more details:

On the brouter...

Yep. I think I got it setup properly...I've assigned it
an IP address...configured it to run IP on ethernet port 0
and turned on SNMP and have given it a read/write community...

I'm still working on this problem...will post more later...

Just wanted ta thank ya guys for the initial response...I get
granular here in few...

more later..

-Stephen
3377.4All set for now.DECWET::WHITESurfin' with the AlienWed Mar 20 1996 13:1622
I still think there may be a MIB problem around the discovery
of brouter 90 modules in a DEChub, and I hope to isolate the
problem and report it here...

but,

very special thanks to Jon Danzak for taking the time
to call me directly and 'hand-hold' me through configuration
and for his free consulting...impressive, very impressive.

This has been one of those 'trail by fire' projects with no
documentation...(OK, .ps output strewn all over my cube)

As I continue to set this up, I'll be sure and continue to post.

thanks to all who helped.

hubwatch is starting to behave properly for me!

the next step is the three T1's...*quaking in my boots*

-Stephen
3377.5Go to that class!PTOJJD::DANZAKPittsburgher �Fri Mar 22 1996 11:2021
    No, silly your next step is TRAINING....and tell that to your manage
    and give him or her this note.
    
    "Training turns POTENTIAL into PERFORMANCE."
    
    I believe that we offered the 3 day training course (only $1k) out
    there in Seattle a few times.  (In fact we have MCS folks from
    Seattle come to Pittsburgh to get trained!)
    
    I'd strongly suggest that trying to set up a multi-channel,
    multi-technology hub with virtual lan capability and per-port
    redirection WITHOUT training is NOT in the best interest of the
    company.
    
    You probably could have cut your hub set-up time in less than half
    which would have more than paid for any training costs as well as
    better armed you to provide better levels of service to your user
    community.
    
    Go to the class!
    j