Conference netcad::hub_mgnt

> -Will it be factory-installed on all the new switches ?
    
    Yes.
    
> -If no, will there be an upgrade-price or is it for free?
    
    No upgrade price -- the new firmware will be placed on the Internet
    for use by anyone who owns a DECswitch.
    
> -Does it work with ALL the DEFBAs or is there a minimum rev. ?
    
    It should work with all supported DEFBAs (ie, no prototypes).
    
> -Does it interoperate with ANY other vendors VLAN capabilities?
    
    No, there isn't a standard currently.  One is being worked upon,
    see below.
    
>-If not, is it possible to build VLANs on DECswitches if there are other
> vendors FDDI parts in the same LAN/WAN
    
    It will not work across routers.  It will work across transparent
    non-VLAN capable FDDI switches, however (for example the GIGAswitch).
    A tag (among other things) is added to the packet which can be decoded
    by another VLAN-aware switch looking at the tagged packet.  The packet
    will be forwarded only to ports which belong to the VLAN identified by
    the tag.  An end station sitting directly on the FDDI will not be able
    to decode such a packet (at least with this release).  A
    "VLAN-challenged" switch will similarly not realize that this is an
    encoded packet.  However the "Default VLAN" capability will allow the
    VLAN function to be introduced in a phased manner (traffic from ports
    belonging to the default VLAN are not tagged).
    
> -Is there already a STANDARD?
    
    No, but IEEE 802 is working on one and Digital is participating in its
    formulation.  This will become the "802.1Q" standard for VLANs.
    (It will be a while before we see a first draft.)
    
> -Is traffic between VLANs routed or some sort of switched?
    
    It needs to be routed.  Think of each VLAN as an instance of a
    bridged LAN.  There are multiple logical bridged LANs running over
    a single physical bridged LAN comprised of VAN-capable switches, which
    are connected to each other via a high-speed backbone or "trunk" (FDDI
    in this case).
    
> -Is there anything to install/configure on the VLAN-clients?
    
    You need the clearVISN VLAN Manager to configure the VLANs.  By
    default, all Ethernet ports will be on the default VLAN and no
    tagging will take place.  In other words things will work like they
    do today if no congiguration is done.  (The manager comes at a price,
    and will be available at least for the Windows NT plaform initially.
    For the price please contact the product manager.)
    
> -Is there any pointer for detailed info(not the "marketing presentation")
    
    Not right now, but manuals are being written as we speak.  I'll try
    and update the switch web page to add VLAN info.
    
    Regards,
    Anil

Hi Anil,

Thx a lot for ya quick response.

Whats the URL of the "switch web page" ?

regards
robi
[Posted by WWW Notes gateway]

    Is VLAN discussed in previous entries also apply to PEswitch 900TX?
    
    Faraday

    >>Whats the URL of the "switch web page" ?
    
    I believe Anil is referring to the NPB web location on this side
    of the firewall, where the DEChub Switch and Bridge Technical Data 
    is discussed.
    
    http://npbww2.hpn.lkg.dec.com/npb/html/hub-switches.html                
    
    
    Bob

    While the pointer that Bob gave has good information on
    switches, the page I was referring to is at (only for use from within
    the firewall):
    
    http://www-dechub.lkg.dec.com:80/internal-info/switches/
    
    Yes, the VLAN function applies to the PEswicth 900TX as well.  It also
    applies to the FIBERswitch 900EF.  However the release on these products
    will likely lag the DECswitch 900EF by some small amount of time,
    on the order of a month.
    
    Anil

Since all traffic between different VLANs has to be routed, what is the
ROUTER box we should sell to our customers. 
-Must this router be on the FDDI and must it be in a DH900 so one can use
 the backplane LANs?
-Does the router have a special "VLAN-routing feature/functionality" or
 can i use e.g. a CISCO or a ??? box.
-How does the router know wether a packet has to be routed or not. 
-Is the DECswitch 900 routing code able to route VLANs or is there a new FW?
-If the server is on the FDDI(default VLAN) and the stations on some other
 VLANs every packet to and from the server has to be routed, so IMHO the
 routing performance is the key thing wether such a scenario works in the
 real world or not. So, how do we address this issue? 
-What is the timeframe for the next steps in EnVisn(class2, class3 VLANs,...)

any help wanted
robert

PS: there is NO info about VLANs in the Switch Web page

[Posted by WWW Notes gateway]

    
    It looks like we never got an answer to this. I have a sales rep
    proposing a VLAN solution with DECswitch 900EFs. The question remains
    is what do I need to configure to route between the VLANs.
    
    For example, I have 2 DEChub 900s with a DECswitch 900EF in each. I
    then make port 1 of each VLAN1. I make port 2 of of each VLAN2. I then
    connect each hub via the FDDI connection on the DECswitch 900EF. How do
    I route between VLAN1 & VLAN2?

    
    	Well I am going to try a cogent 4 port 10/100 PCI ethernet card
    to see if Windows-NT can route between VLANS. I have a similar
    situation and need the ability to support 8 or more VLANS with
    TCP/IP connectivity.
    
    	I have it on order, the EM440-TX, List $998.00 special DEC eval
	price $629.00 30-60 day eval period, for 4 ports of 10/100 is not
	a bad deal, if it works:-)

     I really need Native Multiple VLAN support in our ATMworks 350, but that
    won't be for awhile.