Hi,
Any one else noticed that on the 2950, and I guessing other catalyst low end
switch's, that one cant define the encapsulation of the trunk link. Yes it
will auto negotiate, however I feel that control has been pulled away from
me. I also dont like on the 4006, that you can only define this sa
I read somewhere on cisco.com that the 2950s do not support ISL (it's true,
I tested it) the 2912 and 2924 series support both (2916M need a special
module for trunk), an the 1900XL series just support ISL (also tested). I'm
not sure about the 2820 series but as I think they woul have the same
trun
trunks because you can
do more with traffic prioritization with dot1q headers.
-Original Message-
From: John Brandis [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 20, 2003 9:22 PM
To: [EMAIL PROTECTED]
Subject: cisco 2950 and trunk negotiation [7:63466]
Hi,
Any one else noticed t
The reason that the 2950's do not support ISL trunking is that Cisco is
gradually moving towards supporting the major standards more and proprietary
standards less. As part of this plan they are beginning to make switches
that only support dot1q trunking. At least that's what a TAC engineer told
Systems
- Original Message -
From: "Robert Edmonds"
To:
Sent: Friday, February 21, 2003 6:41 AM
Subject: Re: cisco 2950 and trunk negotiation [7:63466]
> The reason that the 2950's do not support ISL trunking is
that Cisco is
> gradually moving towards supporting the
5 matches
Mail list logo
