I use trunk method, base on the following: http://www.cisco.com/en/US/docs/ios/lanswitch/configuration/guide/lsw_hwic_ethsw_ic_ps6441_TSD_Products_Configuration_Guide_Chapter.html#wp1049866
Hope that can help. On Wed, Sep 2, 2009 at 12:56 PM, Jonathan Charles <[email protected]> wrote: > It is a legacy config because it is an ancient piece of hardware. > > Those of us who have been doing this awhile see it for what it is... a > Cisco 3524XL with only 4 ports. > > > > Jonathan > > On Mon, Aug 31, 2009 at 11:29 PM, Allen Su<[email protected]> wrote: > > Correct Aamir. The reason you need to put the data vlan as native vlan is > > b/c usually frames from PC are not tagged, therefore it needs to be > placed > > in the native vlan of the trunk port. > > > > I actually don't agree that trunk port is the correct config; or I should > > say trunk port is a legacy config method. This is from a Cisco software > > developer for the ISR and HWICs - "vvid is a later feature on hwics, when > > you configure both an access and voice vlan, the port actually behaves as > > trunk port, so mode trunk cli becomes redundant. With vvids, you get some > > qos benefits for ipphones." > > > > Vvid is the voice vlan ID. The above statement is in line with the > config > > guidelines of 3750/3560 that access+voice vlan is the new direction; > trunk > > is legacy. > > > > > http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/1 > > 2.2_35_se/configuration/guide/swvoip.html > > > > Voice VLAN Configuration Guidelines (12.2(35)SE) > > These are the voice VLAN configuration guidelines: > > • You should configure voice VLAN on switch access ports; voice VLAN is > not > > supported on trunk ports. You can configure a voice VLAN only on Layer 2 > > ports. > > Note: Voice VLAN is only supported on access ports and not on trunk > ports, > > even though the configuration is allowed. > > > > > http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/1 > > 2.2_50_se/configuration/guide/swvoip.html > > > > Voice VLAN Configuration Guidelines (12.2(50)SE) > > These are the voice VLAN configuration guidelines: > > • Voice VLAN configuration is only supported on switch access ports; > voice > > VLAN configuration is not supported on trunk ports.You can configure a > voice > > VLAN only on Layer 2 ports. > > Note: Trunk ports can carry any number of voice VLANs, similar to > regular > > VLANs. The configuration of voice VLANs is not required on trunk ports. > > > > > > -----Original Message----- > > From: Aamir Panjwani [mailto:[email protected]] > > Sent: Monday, August 31, 2009 8:02 PM > > To: Jonathan Charles; Michael Ciarfello > > Cc: Allen Su; [email protected] > > Subject: RE: [OSL | CCIE_Voice] ESW phone port configuration - trunk or > > access? > > > > Ok so if me make a trunk port then we must use "native" keyword for data > > vlan...is that correct? > > > > switchport mode trunk > > switchport trunk encapsulation dot1q > > switchport trunk native vlan 100 > > switchport voice vlan 200 > > spanning-tree portfast > > > > > > > > > > > > -----Original Message----- > > From: Jonathan Charles [mailto:[email protected]] > > Sent: Tuesday, 1 September 2009 12:10 PM > > To: Michael Ciarfello > > Cc: Aamir Panjwani; Allen Su; [email protected] > > Subject: Re: [OSL | CCIE_Voice] ESW phone port configuration - trunk or > > access? > > > > The ESW you are referring to is an NM that you have to session over to... > > > > I agree.... I am taking the lab in the morning, and I am making them > trunks. > > > > On Mon, Aug 31, 2009 at 10:12 AM, Michael > > Ciarfello<[email protected]> wrote: > >> Make sure a PC attached to the back of a phone gets the proper data IP > >> address. Those ESW's are built upon 3524's which needed trunk. *I* > would > >> configure trunk. > >> > >> > >> > >> Some ESW's models are based on 3750's which you can only get into via a > >> session command (like Unity express) so you know you would have one of > >> those. The ports don't show up in the router config. > >> > >> > >> > >> > >> > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Aamir > > Panjwani > >> Sent: Monday, August 31, 2009 2:21 AM > >> To: Allen Su; [email protected] > >> Subject: Re: [OSL | CCIE_Voice] ESW phone port configuration - trunk or > >> access? > >> > >> > >> > >> Yes I am curious about this one as well...ipexpert uses trunk port for > ESW > >> module but trunk or access config both works fine as Allen said. > >> > >> > >> > >> If the lab requirement doesn't specifically ask to configure trunk port > > then > >> can we use either method or are there any issues that we need to be > aware > >> of? > >> > >> > >> > >> Thanks > >> > >> > >> > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Allen Su > >> Sent: Thursday, 27 August 2009 3:41 PM > >> To: [email protected] > >> Subject: [OSL | CCIE_Voice] ESW phone port configuration - trunk or > > access? > >> > >> > >> > >> Hi folks, > >> > >> > >> > >> I have a question regarding the phone port configuration on ESW HWIC - > >> should it be configured with trunk or access? > >> > >> > >> > >> Trunk: > >> > >> 1. IPexpert workbook section 1A/1B specifically indicated that the > > ESW > >> phone ports need to be configured as a trunk. > >> > >> 2. The product FAQ said it needs to be configured as trunk > >> > > ( > http://www.cisco.com/en/US/prod/collateral/routers/ps5853/prod_qas0900aecd8 > > 016c026_ps5854_Products_Q_and_A_Item.html) > >> > >> > >> > >> Access: > >> > >> 1. Found another Cisco doc showing access port config > >> > > ( > http://www.cisco.com/en/US/products/hw/modules/ps2797/products_configuratio > > n_example09186a00808066b8.shtml#step4) > >> > >> > >> > >> Tested both in the lab and both seem to be working fine. Phones can > >> register with CME, can get DHCP, etc. > >> > >> > >> > >> Did I miss anything? Will anything not work if it is configured as > access > >> port? > >> > >> > >> > >> > >> > >> Thanks for your help, > >> > >> > >> > >> Allen Su > >> > >> > >> > >> > >> > >> ______________________________________________________________________ > >> This email has been scanned by the MessageLabs Email Security System. > >> For more information please visit http://www.messagelabs.com/email > >> ______________________________________________________________________ > >> > >> ______________________________________________________________________ > >> This email has been scanned by the MessageLabs Email Security System. > >> For more information please visit http://www.messagelabs.com/email > >> ______________________________________________________________________ > >> > >> _______________________________________________ > >> For more information regarding industry leading CCIE Lab training, > please > >> visit www.ipexpert.com > >> > >> > > > > ______________________________________________________________________ > > This email has been scanned by the MessageLabs Email Security System. > > For more information please visit http://www.messagelabs.com/email > > ______________________________________________________________________ > > > > ______________________________________________________________________ > > This email has been scanned by the MessageLabs Email Security System. > > For more information please visit http://www.messagelabs.com/email > > ______________________________________________________________________ > > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
