| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3750.1 | | MXOC00::CSILVA | Carlos@MXO 7296514 Free but focused | Sun Jul 28 1996 15:56 | 33 |
| > I have some question about VLAN, need some help.
> 1. Ports on switch can be assign to different VLAN ?
> what I mean is that if I set port 1on switch A to VLAN 1,can I
> set port 1 and port 2 to VLAN 2 ?
Yes, both the port switches and the MAC-level switches
can do that.
> 2. If my switch has been upgrade to router (DEFBA-DA),can I still
> managed ports by VLAN?
May be the only thing you can administer now
from MultiChassis Manager after the upgrade is to assign
ports to the different VLANs.
> 3. If we use VLAN still we need router ? what I mean is can I use
> VLAN to connect different segment , for example class B address
> to class C address.
It�s the same as having a coax segment with several stations
with different network addresses, you need a router for
the different networks to see themselves.
> 4. VLAN version 1.0 seems only support class 1 VLAN ,when we can
> support class 2 and 3 VLAN ?
The product manager is the right person to answer this.
> 5 .CISCO said their catalyst 5000,1000 can support 1000 more VLAN
> through Fastethernet,FDDI,ATM ,what the "1000 more " means ?
> how many VLANs we can support ? up to hardware ,switch ports ?
May be somebody else can give a better answer to this.
|
| 3750.2 | Not as I understand it ... | SNOFS1::KHOOJEANNIE | Poles are the best post-impressionists | Mon Jul 29 1996 00:55 | 23 |
| > I have some question about VLAN, need some help.
> 1. Ports on switch can be assign to different VLAN ?
> what I mean is that if I set port 1on switch A to VLAN 1,can I
> set port 1 and port 2 to VLAN 2 ?
* Yes, both the port switches and the MAC-level switches
* can do that.
I don't believe we support overlapping VLANs - once port 1 is
assigned to VLAN 1, it cannot also be assigned to VLAN 2.
> 2. If my switch has been upgrade to router (DEFBA-DA),can I still
> managed ports by VLAN?
* May be the only thing you can administer now
* from MultiChassis Manager after the upgrade is to assign
* ports to the different VLANs.
There is no VLAN support in the current DECswitch IP/MP router
software. I thought this was planned for an upcoming release.
Jeannie
|
| 3750.3 | How to find information? | NETRIX::"[email protected]" | Ivan Sorano | Mon Jul 29 1996 09:19 | 17 |
| @ I don't believe we support overlapping VLANs - once port 1 is
@ assigned to VLAN 1, it cannot also be assigned to VLAN 2.
Hmm... this is interesting :)
What's the good reference (book, manual, etc)?
@ There is no VLAN support in the current DECswitch IP/MP router
@ software. I thought this was planned for an upcoming release.
Yes. Use DEFBA with VLAN support to define your VLANs and
DEFBA plus routing for routing between VLANs.
Regards
Ivan
[Posted by WWW Notes gateway]
|
| 3750.4 | Overlapping VLANs, MAX VLAN config | NETCAD::HOPPE | | Mon Jul 29 1996 11:19 | 15 |
| > 1. Ports on switch can be assign to different VLAN ?
> what I mean is that if I set port 1on switch A to VLAN 1,can I
> set port 1 and port 2 to VLAN 2 ?
Overlapping VLANs are not supported in the current release
of VLAN Manager. Therefore, a single switch port cannot
be a member of multiple VLANs.
> 5 .CISCO said their catalyst 5000,1000 can support 1000 more VLAN
> through Fastethernet,FDDI,ATM ,what the "1000 more " means ?
We support up to 250 VLANs. I don't know what CISCO supports.
Chris
|
| 3750.5 | 802.1Q ? | DAIVC::IVAN | | Mon Jul 29 1996 22:37 | 4 |
| Does the Digital's VLAN conform to 802.1Q ?
Regards
Ivan
|
| 3750.6 | | NETCAD::ANIL | | Tue Jul 30 1996 15:12 | 8 |
| No, 802.1Q (Standard for Virtual Bridged Local Area Networks) is far
from completion at this stage -- it is at least a year away. This IEEE
standardization work has started very recently. However we are hooked
into it and will continue to participate so that we can provide a
smooth migration on our products once the standard is done.
Regards,
Anil
|
| 3750.7 | thanks and more ... | HGOM25::WILLIAMBAI | | Tue Jul 30 1996 22:07 | 12 |
|
Many thanks
Now I want back to reality. From our Firmware 1.6 we can support 250
VLANs and from SPD our hardware is 900EF,900FO,PE900switchTX, and my
question is how many VLAN a standalone 900EF,900FO,PE900TX can support?
How to calculate the VLAN number, for example if we want support 32
VLAN how many modules we need ?
William
|
| 3750.8 | More on VLAN | HGOM25::WILLIAMBAI | | Tue Jul 30 1996 22:18 | 6 |
|
And ...
How to implement the VLAN setup ,any else needed in setup?
How to setup route between VLANs ?
thanks.
|
| 3750.9 | ... | SNOFS1::KHOOJEANNIE | Poles are the best post-impressionists | Tue Jul 30 1996 22:21 | 10 |
| Each Ethernet port of the 900EF/900FO/900TX can only be assigned to a single
VLAN, so any of these modules can participate in up to 6 VLANs.
For a network with 32 VLANs, you would need at least 32 switch ports in
theory, but it doesn't make any sense unless you have at least 2 switch
ports in each VLAN ... so at least 64 switch ports in total.
Rgds
Jeannie
|
| 3750.10 | Oops, .8 just posted | SNOFS1::KHOOJEANNIE | Poles are the best post-impressionists | Tue Jul 30 1996 22:51 | 14 |
| Re .8
To set up the VLANs, you would use clearVISN VLAN Manager.
To route between VLANs, the router would need to be connected to the
Ethernets that are members of the various VLANs.
There would be no change to the Ethernet devices - when they need to talk to
devices on a different subnet, they would use their default gateway as
normal.
Jeannie
|
| 3750.11 | Vlan Manager and the maximum number of user-defined VLANs supported per switch | NETCAD::GILLIS | | Wed Jul 31 1996 15:10 | 22 |
| Member ports are ETHERNET only, and at least one port on every switch in
the VLAN topology has to belong on the default VLAN. Therefore, a maximum
of 5 ports per switch can be assigned to separate VLANs.
If you want 32 VLANs ....
Trivial Case
------------
32 member ports give you 32 unique VLANs ... they can all talk to
each other over the default VLAN, but this buys you nothing. It's the
same as having no VLANs at all. Requires 7 switches in the VLAN topology.
Minimum Case
------------
At a minimum, requires two member ports from any switch in the
topology to be in the same VLAN. 64 member ports accomplishes this, which
requires 13 switches in the topology.
John Gillis
clearVISN development
|
| 3750.12 | Default VLAN ports | NETCAD::HOPPE | | Wed Jul 31 1996 19:45 | 27 |
| >Member ports are ETHERNET only, and at least one port on every switch in
>the VLAN topology has to belong on the default VLAN. Therefore, a maximum
>of 5 ports per switch can be assigned to separate VLANs.
This is not completely true. One port on every switch does NOT
have to belong to the default VLAN. The only ports that must
remain in the default VLAN are ports that your network
management stations are connected to. If your network
management stations are connected directly to the FDDI
backbone, no ports have to be in the default VLAN.
>32 member ports give you 32 unique VLANs ... they can all talk to
>each other over the default VLAN, but this buys you nothing. It's the
>same as having no VLANs at all. Requires 7 switches in the VLAN
>topology.
I may have misunderstood what you said here, but if you have
32 member ports configured into 32 unique VLANs, they
will not be able to talk to one another over the default VLAN.
The default VLAN is treated as a seperate VLAN.
So, realizing that you may not need as many default VLAN ports
as last calculated, you can actually get away with
12 switches for 32 VLANs.
Chris
|
| 3750.13 | | SNOFS1::KHOOJEANNIE | Poles are the best post-impressionists | Wed Jul 31 1996 22:59 | 26 |
| > This is not completely true. One port on every switch does NOT
> have to belong to the default VLAN. The only ports that must
> remain in the default VLAN are ports that your network
> management stations are connected to. If your network
> management stations are connected directly to the FDDI
> backbone, no ports have to be in the default VLAN.
Just to check that I have it straight, is this because the network
management of the DECswitches is somehow tied to the FDDI port?
(e.g. when you manage the DECswitches, they always use the MAC address
of the FDDI port, no matter whether you come in via the FDDI port or an
Ethernet port)
If, for example, you had the net mgmt station on Ethernet VLAN 3, you
wouldn't be able to manage any native FDDI devices, but:
- can you manage other DECswitches that also have an Ethernet port
in VLAN 3?
- can you manage other DECswitches that don't have an Ethernet port
in VLAN 3?
64/6 = 11 switches (?)
Jeannie
|
| 3750.14 | D'oh! | SNOFS1::KHOOJEANNIE | Poles are the best post-impressionists | Wed Jul 31 1996 23:02 | 6 |
| Oops, forgot to ask something else ...
In the case with the net mgmt station in VLAN 3, and whether you can
manage DECswitches that don't have an Ethernet port in VLAN 3, would
it make any difference if there was a router between all the VLANs?
|
| 3750.15 | Default VLANs and NMSs | NETCAD::HOPPE | | Thu Aug 01 1996 19:17 | 40 |
| > Just to check that I have it straight, is this because the network
> management of the DECswitches is somehow tied to the FDDI port?
>
> If, for example, you had the net mgmt station on Ethernet VLAN 3, you
> wouldn't be able to manage any native FDDI devices, but:
>
>
> - can you manage other DECswitches that also have an Ethernet port
> in VLAN 3?
>
> - can you manage other DECswitches that don't have an Ethernet port
> in VLAN 3?
The rule to follow is that if you have your NMS on a non-default
VLAN port (like in the example you have above), you will not
be able to communicate with any devices that are connected
directly to the FDDI ring. Packets that come in the FDDI
interface destined to the DECswitch itself are considered
to be in the default VLAN. Therefore, the DECswitch's
reply going out the FDDI interface will also be considered
as in the default VLAN. So, the reply will never reach the NMS.
> 64/6 = 11 switches (?)
oops :) that's true, then you'd still have 2 default VLAN ports.
> In the case with the net mgmt station in VLAN 3, and whether you can
> manage DECswitches that don't have an Ethernet port in VLAN 3,would
> it make any difference if there was a router between all the VLANs?
This should work. You could place your NMS on VLAN 3 and place
a router between VLAN 3 and the default VLAN. Then, the NMS
should be able to communicate with all devices attached directly
to the FDDI ring. I've never actually tried this, though.
Chris
|
| 3750.16 | Servers on FDDI should be VLANned | MOSCOW::FELIZHANKO | Things can only get better... | Fri Aug 02 1996 04:38 | 11 |
| 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 tagged FDDI frames and process them
properly. One "public" server 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?
Alex
|
| 3750.17 | VLAN Name <-> Frame Tag, How? | SNOFS1::KHOOJEANNIE | Poles are the best post-impressionists | Tue Aug 06 1996 04:41 | 22 |
| re -.1, I spoke to FDDI NIC engineering during the SE Forum last month
and there were no plans to do this - I think we'll have to wait for the
MAC layer VLANs.
Yet another question on VLANs ...
How does VLAN Manager/DECswitch get from the VLAN name to the frame tag that
is used?
For example, if you create VLANs on one switch using one clearVISN PC
(say VLAN1 and VLAN2) and then on another clearVISN PC you create VLANs
on another switch also called VLAN1 and VLAN2, will these automatically
get the same frame tag, and thus interwork properly when you connect
them together?
I tried this out and it *appeared* to work - is it an algorithm based on
the characters in the VLAN's name?
Thanks
Jeannie
|