[cisco-voip] "switchport" command behavior on 3500XL

[Brian Feeny]

Thanks,

Numerous configs/examples I see show 4000's and other IOS based doing  
access mode, yet have "switchport trunk encapsulation dot1q".  They  
don't specifically have "switchport mode access" configured, yet they  
don't have "switchport mode trunk" configured either, so I would  
think that puts it into access mode (could check with sh int fx/x  
switchport)

Brian

On Aug 27, 2005, at 1:06 PM, Nikola Stojsin wrote:

> It really, really depends on what version of IOS the switch runs— 
> the recommended configuration has changed a lot over the years.
>
> The field notice below lists (at the very bottom) the latest (that  
> I know of—it is from November 2004) recommended configuration—it is  
> for 3500XLs running IOS version 12.0(5)WC and later:
>
> http://www.psionic.com/en/US/products/hw/phones/ps379/ 
> products_field_notice09186a008031575e.shtml
>
>
>
> By way of comparison, the following book excerpt lists the  
> recommended configuration from around July 2003 (it also gives a  
> brief overview of hardware capabilities of the switches):
>
> http://www.ciscopress.com/articles/article.asp?p=98122&seqNum=3&rl=1
>
>
>
> Hope this helps!
>
> Nikola Stojsin
>
>
>
>
>
> ---------------------------------------------------------------------- 
> ------
>
> Nikola Stojsin
>
> PhD CCIE#12888
>
> nikola at att.net
>
> -----------------------------------------------------------------
>
>
>
>
>
>
>
>
>
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip- 
> bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
> Sent: Saturday, August 27, 2005 11:37 AM
> To: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] "switchport" command behavior on 3500XL
>
>
>
>
>
> here's what we have. it's done us well. we had (and are still  
> working out I believe) some issues with QoS on these older  
> switches. some of the guys on the team investigated and determined  
> the allowed vlans should be modified for a more efficient/secure  
> delivery. vlan 129 and 131 are our mgmt networks, that's why there  
> were deleted. i'm sure we could have gone further and only allowed  
> 1 (default, can't remove) the voice and data vlans and (1000-1005,  
> can't remove these either i think).
>
>
>
> interface FastEthernet0/3
>  switchport trunk encapsulation dot1q
>  switchport trunk native vlan 226
>  switchport trunk allowed vlan 1-128,130,132-1005
>  switchport mode trunk
>  switchport voice vlan 938
>  switchport priority extend cos 0
>  spanning-tree portfast
>
> ---------------------------------------------------------------------- 
> ----------
> Lelio Fulgenzi, B.A.
> Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "I had a coffee and Coke at lunch today...and now, I've got more  
> jitter than an
> IP phone on a long haul 10base2  
> connection"                                           LFJ
>
> ----- Original Message -----
>
> From: Brian Feeny
>
> To: cisco-voip at puck.nether.net
>
> Sent: Saturday, August 27, 2005 1:34 AM
>
> Subject: [cisco-voip] "switchport" command behavior on 3500XL
>
>
>
>
> I have a question regarding the behavior of some "switchport"
> commands on the 3500XL vs. other cisco switches.
>
> On a 4000 (IOS) you can do:
>
> switchport trunk encapsulation dot1q
> switchport access vlan 100
> switchport voice vlan 200
>
> And that will allow you to:
>
> connect a regular device, and it will use vlan 100
> connect a cisco phone and it will trunk, placing the phone into vlan
> 200, and device connected thru the phone into vlan 100
>
> But on a 3500XL, which supports those same commands, it apparently
> does not behave that way.  You have to do:
>
> switchport trunk encapsulation dot1q
> switchport mode trunk
> switchport access vlan 100
> switchport voice vlan 200
>
> which then allows the phone to work as you would expect, but a PC
> connected directly to the switch will not work so you have
> to add the native vlan:
>
> switchport trunk encapsulation dot1q
> switchport trunk native vlan 100
> switchport mode trunk
> switchport access vlan 100
> switchport voice vlan 200
>
> which once you have done that, doesn't even make sense to have
> "switchport access vlan 100", so end up with:
>
> switchport trunk encapsulation dot1q
> switchport trunk native vlan 100
> switchport mode trunk
> switchport voice vlan 200
>
> I am just trying to nail down what config I should use to allow the
> port to be used directly by a device such as a PC, and also allow it
> to trunk to a cisco phone that would carry voice/data vlans.  It
> seems these commands change alot as IOS gets updated.  What is the
> correct configuration to do what I am wanting on the 3500XL?
>
> Brian
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050828/ec8e09e1/attachment.html