[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

4290.0. "Firmware upgrade,lan interconnect-->WEIRD" by PTOJJD::DANZAK () Tue Mar 18 1997 10:20

    
    I noted the following with LAN interconnect and the new V5 MAM.  It
    appears that when upgrading firmware in a module (it doing a reset) and
    with autohealing disabled, weird stuff happened to OTHER modules in the
    hub.
    
    Aarugh.
    
My hub has the following config:


1  Roamabout
2
3
4
5  DECconcentrator 900MX V2.4 or something
6  DECswitch 900EF V1.7 (latest)
7  DECconecntrator 900MX V3.3.4 (latest)
8  DECrepeater 900TM (latest) Ip services module


I noticed odd LAN interconnect behaviour after upgrading some other
concentrators. i.e. after the concentrator RESET it was disconnected 
(i.e. firmware upgrade RESET the concentrator and it lost it's LAN
connections.)

Note, auto healing was NOT enabled.

I upgraded the module in slot 5...and, it lost it's LAn connect.
Also, the DECswitch 900EF appeard to loose it's connect as well as the
concentrator.

A REFRESH to get status, etc., and I tried to reconnect the
modules, etc.  The configs on the screen did *NOT* match the
light state. i.e. the DECswitch and concentrator in slots 6&7 showed
DISCONNECT but their LIGOtype showed CONNECT.

I mucked a bit, connecting and disconnecting the FDDI...but at one
point the connection to thinwire from the 900TM in slot 8 went away!
(at that point, even removing and reinserting the 900TM did *NOT*
reinstate it's default connect...)  (Sounds like it tried to
autoheal in spite of NO autoheal...almost...)

My only recourse was to reset to FACTORY defaults.

I was upgrading lots of concentrators, noticed that the
FDDI of OTHER modules got disconnected when the concentrator
being upgraded reset.  Didn't think much of it at first until
I noticed that the LAN light on the concentrator in slot 7 was
going out - even tho it should not have been effected.

(i.e. I kept slot 7 and 8 in the FDDI ring because if I upgraded a
concentrator - i would loose the slot 7 connect because of no FDDI
neighbor...so I wanted 2 FDDI modules permanently connected to keep
my backplane ring up etc. 
    
    
T.RTitleUserPersonal
Name
DateLines
4290.1NETCAD::MILLBRANDTanswer mamTue Mar 18 1997 13:203
What version of MCM are you running?

	Dotsie
4290.2It was V5.PTOJJD::DANZAKTue Mar 18 1997 19:224
    V5.0
    
    NOT any FT version but the shipping V5.0.
    
4290.3NETCAD::MILLBRANDTanswer mamWed Mar 19 1997 19:114
MCM V5.0 and MAM V5.0 do not work together.  Upgrade hub to V5.0, then upgrade 
MCM to V6.0a, then upgrade modules.  LAN Interconnect will be much happier.

	Dotsie
4290.4It WAS the latestPTOJJD::DANZAKThu Mar 20 1997 10:269
    Er, I got confused....it was ALL the latest version.....
    
    MAM version 5
    CLEARvisn V1.1a which has
    MCM V6
    
    Or something like that