[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

3770.0. "VLANned servers on FDDI?" by MOSCOW::FELIZHANKO (Things can only get better...) Mon Aug 05 1996 04:18

Can we expect smart enough FDDI NIC driver/software allowing servers on FDDI
to participate in clearVISN VLANs?

In fact, VLANs have no meaning unless your servers sit on a high-speed uplink/
backbone and serve clients that can belong to different VLANs. That means the
server with DEFPA should understand cVISN (i.e. proprietary for the time being,
802.1Q in the future) tagged FDDI frames and process them properly.
One "public" server on FDDI should support multiple VLANs on one NIC without
routing just to provide common public services (file, print, mail etc.) to the
clients. Is this in our plans? Or, at least, is our NIC team a part of enVISN/
clearVISN program?

For instance, in the "3Com Transcend VLANs" brochure (http://www.3com.com/
0files/strategy/537VLAN.html) we read "Transcend VLANs provides the ability
to make servers members of more than one VLAN ... It can be done for Fast
Ethernet attached servers via VLT (i.e.Virtual LAN Trunking - proprietary)
support in the 3Com server NIC and driver. For Fast Ethernet attached servers,
Phase 2 will add support for the 802.1Q tagging...".

Alex
T.RTitleUserPersonal
Name		DateLines
3770.1NETCAD::ANILTue Aug 06 1996 14:5012
    My understanding is that the NIC group will look at implementing
    the 802.1Q standard for VLANs on trunk end-stations, but as mentioned
    elsewhere this standard is a work in progress.  We are also looking
    at what it would take in a later VLAN release to have non-VLAN aware
    servers and end-stations residing on trunks participate in VLANs.
    However this is under study; until it is actually implemented, the
    only way now to include servers on a VLAN tagged trunk is by putting it
    on a port and including it by port policy; or by putting it on the
    DECswitch's default VLAN, which has no tagging associated with it.
    
    Regards,
    Anil
3770.2MOSCOW::FELIZHANKOThings can only get better...Wed Aug 07 1996 04:0118
Anil,

>   at what it would take in a later VLAN release to have non-VLAN aware
>   servers and end-stations residing on trunks participate in VLANs.

Simply can't imagine how "non-VLAN aware servers" can participate in VLANs.
For me, there could be only two options. First, servers should be VLAN aware
(DEFPA + software) as mentioned in .0. Second, GIGAswitch/FDDI should perform
tagged frame processing and send out original frames to non-VLAN aware servers.

>   on a port and including it by port policy; or by putting it on the
>   DECswitch's default VLAN, which has no tagging associated with it.

I didn't get what port you mean. As for putting a public server on the
default VLAN, all the clients must be on the default VLAN also that is
no VLANs at all.

Alex
3770.3NETCAD::ANILWed Aug 07 1996 14:2520
> Simply can't imagine how "non-VLAN aware servers" can participate in VLANs.
> For me, there could be only two options. First, servers should be VLAN aware
> (DEFPA + software) as mentioned in .0. Second, GIGAswitch/FDDI should perform
> tagged frame processing and send out original frames to non-VLAN aware servers.
    
    Since this is "futures" (rather than something available now)
    and is still in the architecture phase, I'd prefer not to get into
    it too much here.  However I wanted to let you know that we understand
    and are trying to address this issue.
    
> >   on a port and including it by port policy; or by putting it on the
> >   DECswitch's default VLAN, which has no tagging associated with it.
>
> I didn't get what port you mean.
    
    If you put a server on one of the Ethernet switch ports which comprise
    a VLAN, then it becomes dedicated to that VLAN.  This may not always
    be the best solution, but it is one possible approach.
    
    Anil
3770.4ThanksMOSCOW::FELIZHANKOThings can only get better...Thu Aug 08 1996 04:1211
Anil,
    
>    If you put a server on one of the Ethernet switch ports which comprise
>    a VLAN, then it becomes dedicated to that VLAN.  This may not always
>    be the best solution, but it is one possible approach.

It's clear but not useful for powerful servers. Also, such a server would
serve only one not multiple VLANs.

Thank you anyway,
Alex