I'm not clear on which standard I should use for VLAN setup.
I will be using a 2948G-L3 as a core switch. Connected to the core
will be a number of 2948xl as access switches. The majority of these
access ports will connect directly to end stations, though some will
connect to other 2948s (via
Hi
ISL is cisco stuff ..if ur network is all cisco you can use ISL in that
but if it involves other switches or in near future u see this thing use
Dot.1Q.This is for the equipment ..and for the performance thing which one
is better i thing somebody more experienced can help u on this .
Hi Sammi,
Indeed, ISL is Cisco propietary, so should you consider other vendor's
switches in your network, now or in the future, I'd recommend 802.1q. Beware
however, dot1q has some drwabacks with regards to loops. Check out
On 23 Jul 2001 08:53:26 -0400, [EMAIL PROTECTED] (Remmert Veen)
wrote:
If not (so your network is all Cisco) you might wanna consider ISL.
Thanks, my network is indeed all Cisco.
If an environment is ISL, is it a safe assumption one would need to
redo all switches if you started to introduce
. And on the flip side, not all of Cisco's switches support
802.1Q (like the 1900 series switch).
-- Leigh Anne
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Sammi
Sent: Monday, July 23, 2001 9:14 AM
To: [EMAIL PROTECTED]
Subject: Re: VLAN: ISL or 802.1Q
At 08:53 AM 7/23/01, Remmert Veen wrote:
Hi Sammi,
Indeed, ISL is Cisco propietary, so should you consider other vendor's
switches in your network, now or in the future, I'd recommend 802.1q. Beware
however, dot1q has some drwabacks with regards to loops. Check out
The switches you have support both ISL and Dot1Q if you are running the
enterprise code, not sure for the standard stuff. For a sample config:
http://www.cisco.com/warp/public/473/43.html
Hope that helps.
Arun wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Hi
ISL is cisco
I haven't thought through the STP part yet, but the first section I
understand. In ISL, *all* frames are tagged. However, in 802.1q, the
native VLAN is not tagged. The switch (or router) must assume that all
untagged frames belong to the native VLAN.
If Switch A has VLAN1 as its native VLAN,
Priscilla,
A native VLAN is the VLAN that a port functions under when its not trunking.
When the switch comes online one of the things it does is perform any
negotiations for trunking. In order to negotiate the two ports need to be
able to communicate at layer 2. If the ports at either end of
Ah, so I was incorrect in assuming that mayhem and chaos might ensue if
there were a native VLAN mismatch. I thought that traffic from one VLAN
might be mixed with traffic from the other VLAN. But if I understand
you correctly, they would never actually begin trunking in the first
place, right?
-giants which non-Cisco switches will see as errors.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Remmert Veen
Sent: Monday, July 23, 2001 8:53 AM
To: [EMAIL PROTECTED]
Subject: RE: VLAN: ISL or 802.1Q? [7:13325]
Hi Sammi,
Indeed, ISL is Cisco
Thanks for the config sample, and thank you all for the input.
I'm drawn to 802.1Q, although I can't really give exact reasons.
During the transition I will have a few 1900 and a couple of 2800
switches in the network and it seems I'll have less trouble with the
802.1Q.
On 23 Jul 2001 15:39:43
At 09:53 PM 7/23/01, Sammi wrote:
Thanks for the config sample, and thank you all for the input.
I'm drawn to 802.1Q, although I can't really give exact reasons.
During the transition I will have a few 1900
I don't think the 1900s support 802.1q!? That will be your first problem.
Priscilla
On 23 Jul 2001 22:16:17 -0400, [EMAIL PROTECTED] (Priscilla
Oppenheimer) wrote:
At 09:53 PM 7/23/01, Sammi wrote:
Thanks for the config sample, and thank you all for the input.
I'm drawn to 802.1Q, although I can't really give exact reasons.
During the transition I will have a few 1900
I don't
14 matches
Mail list logo
