Conference netcad::hub_mgnt

    You didn't state what firmware rev the DECswitch 900EF is at.
    IE: FW=???
    You provided the HW rev, and RO rev but no FW rev. This might be
    the important piece of information needed.
    
    Bob

    oops, sorry about that, the module was not manageable at version
    v1.5 or after upgrading it to 1.7.
    
    
    
    Thanks
    
    Rich Stewart

The symptoms are what you would see if you had a version
mismatch between the hub (MAM) and MCM. I realize
you say you upgraded the hub before using the 
new MCM. But those are the symptoms.

I would try exiting MCM, and then restarting it.

If that doesn't work, make sure auto-healing is turned off,
exit MCM,  and then physically remove and reinsert the 
decswitch 900ef. Then start MCM again.

If that doesn't work, you pretty much have no choice but
the use the "reset-to-factory-defaults" big hammer.

I would like to know the precise steps you (or the customer)
took to get it in that state. I can try it with my hub.

-Mike

    Hi Mike,
    
    	I sent mail to the customer to get the steps he took when he
    upgraded and will have him try your other suggestions, I will let
    you know as soon as I hear back from him.
    
    Thank you
    
    Rich Stewart

    DH900MS, 3 Power Supplies, 3 900TM Repeaters, and 1 900EF
    Switch.  They are layed out as follows:
    Slot1-empty
    Slot2-empty
    Slot3-empty
    Slot4-empty
    Slot5-900TM Repeater (setup as LAN #2)
    Slot6-900TM Repeater (setup as LAN #1 with 900TM in slot#8)
    Slot7-900EF Switch
    Slot8-900TM Repeater (setup as LAN#1 with 900TM in slot#6)
    
    After purchasing the DH900MS ~2 years ago,
    I started filling slots from right to left (8 to 1).
    So the 900TM in Slot8 was used in management mode,
    to access the Hub and other modules.
    
    When I upgraded the DH900MS firmware,
    from V3.1.0 to V5.0,
    I did so through a 900TM Repeater which was at Firmware Rev 1.1.0.
    The DH900MS firmware apparently took,
    because the LCD of the DH900MS displayed the new version.
    I next tried to upgrade the 900EF.
    This too apparently took,
    as the 900EF did display the correct firmware when queried thru
    ClearVISN or local console.
    It was after this that I noticed that I could no longer
    control the direction of the switch ports (either "in" or "out"),
    and the dialog that is supposed to display the status of the port
    direction,
    only displays blank buttons.
    
    This is when we got a new 900EF,
    thinking that the other was in a funk,
    and the same problem exists in this 900EF.
    That is, the problem of managing the 900EF port redirection.
    It is interesting to note however,
    that on my old 900EF switch,
    I could not redirect Port3 of the 900EF to the backplane,
    but on the new 900EF,
    ClearVISN reports all ports as pointed inward,
    even when Ports 4,5,6,&7 are pointed outward and working.
    
    In fact,
    I am trying to switch in another segment right now,
    and I'm trying to connect to Port2 on the 900EF.
    And I can't even get it to work,
    either in inward mode to LAN#2 on the backplane,
    or in outward mode, through a transciever and RJ45 crossover into the
    900TM repeater in Slot5
    
    Right now,
    all my modules are at current firmware levels,
    and I'm managing thru another 900TM repeater.
    
    I need to get this resolved shortly,
    as I need to switch in a new segment about yesterday.
    
    I also have a requisition in for 3 VN900EX's, plus some 612 and 624
    modules.
    So, I want to get the current problems behind me,
    before I work on the new crop of issues,
    that are certain to come up.
    
    I've already reset the hub, reset the bridge,
    tried different management repeaters.
    

What version of ClearVISN are you using? After upgrading to V5.x of the 
MAM code, you should be using V1.1a of ClearVISN, which has V6 of MCM.
If you are trying to use ClearVISN V1.0 or Hubwatch Vx.x, you won't 
have much success with lan interconnects.

Brad

    
    Hi Brad,
    
    	I included this information in the base node, V1.1A is what the
    	customer is running.
    
    Rich

Sorry Rich, I only read note .5

Brad