[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

4288.0. "MCM V6.0, port number not visible" by ROM01::GALLANA (Francesco Gallana) Tue Mar 18 1997 06:07

    In the MCM V6.0 , expanding the "port configuration" of a
    DECswitch900-EF (as an example) the "port number" parameter is not 
    visible... is it a bug?
    
    Thanks
    
    Francesco
T.RTitleUserPersonal
Name
DateLines
4288.1which MCM view?NETCAD::MOWERTue Mar 18 1997 22:2511
>    In the MCM V6.0 , expanding the "port configuration" of a
>    DECswitch900-EF (as an example) the "port number" parameter is not 
>    visible... is it a bug?
    
 Francesco,
   Could you be a little more specific?  Which MCM view - the switch summary
   view?

 Carl.

4288.2Use the "Station Configuration" (Switch summary wind)ROM01::GALLANAFrancesco GallanaWed Mar 19 1997 04:3418
    Carl,
    
    I'm sorry for the general description of the problem
    
    The window is the "Station Configuration" lanched from the Switch
    summary
    
    You get the same informations starting from the "Lan Interconnect"
    windows and selecting the DECswitch900EF and then the "Config" button.
    
    Second thing: It isn't so useful to have all the DECswitch 900EF ports 
    (external and internally switched) visible in the Lan Interconnect
    window because you can, if not aware, to connect an externally
    connected port to an internal channel; it was better before... only the
    manually switched port was visible in the Lan Interconnect window.
    
    Regards
    Francesco
4288.3need even more informationNETCAD::MOWERWed Mar 19 1997 23:1933
    
>    The window is the "Station Configuration" lanched from the Switch
>    summary
>    
>    You get the same informations starting from the "Lan Interconnect"
>    windows and selecting the DECswitch900EF and then the "Config" button.

  I think I still don't understand the problem.  I lauched the "station 
  configuration" view for a DECswitch 900EF from both the "switch summary"
  and "LAN Interconnect" views, and got identical views.  Additionally, 
  they both correcty showed the "Port Number" data no matter how I re-sized
  the window.  I did the same with the VN-EF.  Am I missing something here,
  or is this not reproducable?

    
>    Second thing: It isn't so useful to have all the DECswitch 900EF ports 
>    (external and internally switched) visible in the Lan Interconnect
>    window because you can, if not aware, to connect an externally
>    connected port to an internal channel; it was better before... only the
>    manually switched port was visible in the Lan Interconnect window.

  For both the DECswitch and VNswitch modules, each port is either active on
  the front panel of the device or turned to the backplane where it may or
  may not be connected to a backplane LAN.  I don't understand your statement
  "connect an externally connected port to an internal channel",

  I also do not understand "it was better before" - we have tried to keep the
  same functionality from clearVISN v1.0.


  I want to help, but need still more explanation.
  Carl.    

4288.4V1.7.0 and V1.7.0R are treated differentlyROM01::GALLANAFrancesco GallanaWed Apr 02 1997 12:0118
    Carl,
    
    I'll be more precise...
    
    The problem is visible when the "Station Configuration" is launched on
    a DECbridge 900MX with firmware V1.7.0; there are no problems on a
    DECbridge 900MX with firmware V1.7.0R
    
    Same behaviour with the LAN interconnect: try to see the LAN
    interconnect in a HUB with DECbridge 900MX running V1.7.0; you will see
    all the ports switched "internally".
    I tried both MCM V5.0 and V6.0A and they show different things.
    
    Waiting for your tries
    
    Francesco
    
    My version of MCM is V6.0A
4288.5Is it a DECbridge or a DECswitch you have?NETCAD::BATTERSBYWed Apr 02 1997 14:4218
    Francesco, I'm a little confused as to what hardware you have
    that exhibits this problem. In an earlier reply you mention
    "DECswitch900EF" hardware being used, and then in reply .5
    you mention "DECbridge900MX" hardware. There are differences
    in this hardware, and when we see comments on a problem related
    to one type of hardware certain things come to mind as to what
    the problem might be. When an older rev of hardware is mentioned,
    a different set of thoughts crosses ones mind.
    So can you help us a bit by clarifying and confirming which hardware 
    rev/type you are seeing this problem on.
    
    Just so you know why I'm asking for this confirmation, the DECbridge 
    900MX has more than just the difference of a bezel name change.
    There are many differences in the hardware revision of the internal 
    Processor module and I/O module relative to the current hardware rev 
    being shipped in the DECswitch 900EF.
    
    Bob
4288.6DECbridge and DECswitch, same behaviourROM01::GALLANAFrancesco GallanaThu Apr 03 1997 05:5117
    Bob,
    
    I agree with you about the differences between DECbridge 900MX and
    DECswitch 900EF...
    
    I did my tries on a DECbridge 900MX and today, after your reply, even
    on a DECswitch 900EF; same behaviour: firmware version V1.7.0 exhibit
    the problem while DECbridge 900MX and DEcswitch 900EF with fw V1.7.0R
    don't.
    
    I'm more precise:  DECswitch 900EF HW=V1/2, RO=V0.4, SW=V1.7.0
    		       DECswitch 900EF HW=V1/2, RO=V0.4, SW=V1.7.0R
    		       DECbridge 900MX HW=V0/1, RO=V0.2, SW=V1.7.0
    		       DECbridge 900MX HW=V0/2, RO=V0.2, SW=V1.7.0R	
    
    Regards
    Francesco