Carmelo,
You might want to double check trunking support on that cat 4000. Some
models do not support ISL and only have Dot1Q support.
Regardless, it would be better to only have one trunking type on the
network, if only for troubleshooting purposes.
Hope this helps,
Karen
***
per-VLAN STP maybe?
Andy
- Original Message -
From: "Gareth Hinton"
To:
Sent: Wednesday, May 09, 2001 9:45 PM
Subject: Re: Encapsulation V-LAN [7:3798]
> I would say use dot1q everywhere.
> ISL will disappear at some point in the future. Big overheads compared to
&g
You did not mention it, but I assume you have sub interfaces with ISL
encapsulation on
the routers , the same as the VLAN os the switches..
What happens when you do a "sh stan" from each router ?
andyh wrote:
> if you have a Cisco-only switch architecture I would use ISL between the
> Catalysts
if you have a Cisco-only switch architecture I would use ISL between the
Catalysts - per-vlan STP is *VERY* useful for resilience and load-balancing
purposes.
I would use dot1q for attached servers where necessary - since they are
end-stations there is not the requirement for them to participate
01 3:45 PM
To: [EMAIL PROTECTED]
Subject: Re: Encapsulation V-LAN [7:3798]
I would say use dot1q everywhere.
ISL will disappear at some point in the future. Big overheads compared to
dot1q.
Anybody have any valid reasons to stay with ISL?
Gaz
""carmelo Garofalo"" wrote in m
I would say use dot1q everywhere.
ISL will disappear at some point in the future. Big overheads compared to
dot1q.
Anybody have any valid reasons to stay with ISL?
Gaz
""carmelo Garofalo"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi Guys,
> i have a question for you.
>
>
>
>Hi Guys,
>i have a question for you.
>
>In my site i have to project a new network architecture.
>
>I would organize the Resource human in V-LAN. Of course all V-LAN have to
>access some services (example DNS, E-Mail, Domain Controller etc. etc) and
>not others.
>
>The NIC interfaces of my serv
7 matches
Mail list logo