Hi Team, I believe once you configure a port as access you can not configure it as trunk port. In order to configure it as trunk port, you have to configure encapsulation also. Moreover concept of native vlan is proposed with Dot1Q tunnel. So this port will be considered as trunk port.
Thanks, Pradeep On Sat, Mar 5, 2011 at 11:48 AM, <[email protected]>wrote: > Send CCIE_RS mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://onlinestudylist.com/mailman/listinfo/ccie_rs > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CCIE_RS digest..." > > Today's Topics: > > 1. Re: "switchport access vlan" and "switchport trunk native > vlan" (Marko Milivojevic) > 2. (ccie_rs) native vlan ([email protected]) > 3. Re: (ccie_rs) native vlan (Dwann Hall) > 4. Re: (ccie_rs) native vlan ([email protected]) > 5. hostname mismatch (cyrus riobah) > 6. Re: (ccie_rs)_native_vlan ([email protected]) > 7. Re: hostname mismatch (marc abel) > 8. Re: (ccie_rs)_native_vlan (Michael Smith) > 9. Volume 2 lab 2 Task 9.1 (Michael Smith) > 10. Re: (ccie_rs)_native_vlan (Kurt Bales) > > > ---------- Forwarded message ---------- > From: Marko Milivojevic <[email protected]> > To: venkat <[email protected]> > Date: Fri, 4 Mar 2011 09:51:29 -0800 > Subject: Re: [OSL | CCIE_RS] "switchport access vlan" and "switchport trunk > native vlan" > That is correct. > > -- > Marko Milivojevic - CCIE #18427 > Senior Technical Instructor - IPexpert > > FREE CCIE training: http://bit.ly/vLecture > > Mailto: [email protected] > Telephone: +1.810.326.1444 > Web: http://www.ipexpert.com/ > > On Fri, Mar 4, 2011 at 07:15, venkat <[email protected]> wrote: > > > Hi , > > > > If an L2 interface has following configuration and if it receives an > > untagged packet on this interface, will it consider as vlan 10 or vlan 20 > > packet? My understanding, is if the port is negotiated as access, the > > packets will be for vlan 10 and if it negotiates to trunk the packets > will > > be for vlan 20. Please confirm. > > > > Router(config-if)#do show run int gi 2/30 > > Building configuration... > > > > Current configuration : 109 bytes > > ! > > interface GigabitEthernet2/30 > > switchport > > switchport access vlan 10 > > switchport trunk native vlan 20 > > end > > > > Router(config-if)# > > > > > > Thanks, > > Venkat > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, please > > visit www.ipexpert.com > > > > > > ---------- Forwarded message ---------- > From: "[email protected]" <[email protected]> > To: "[email protected]" <[email protected]> > Date: Fri, 04 Mar 2011 18:54:37 +0000 > Subject: [OSL | CCIE_RS] (ccie_rs) native vlan > Hi > iread that native vlan is vlan 1 by default in switch but i want to know > that What does native vlan do? And what is importance it has? > And at last why should we not change native vlan for best practice? > > Regards > narendra > > > > ---------- Forwarded message ---------- > From: Dwann Hall <[email protected]> > To: "[email protected]" <[email protected]> > Date: Fri, 4 Mar 2011 15:27:42 -0500 > Subject: Re: [OSL | CCIE_RS] (ccie_rs) native vlan > native vlan = no vlan tag, the vlan id is stripped as traffic egresses > the port and the vlan id is inserted as untagged traffic ingresses the > port. > > On Fri, Mar 4, 2011 at 1:54 PM, [email protected] > <[email protected]> wrote: > > Hi > > iread that native vlan is vlan 1 by default in switch but i want to know > that What does native vlan do? And what is importance it has? > > And at last why should we not change native vlan for best practice? > > > > Regards > > narendra > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > > > > > ---------- Forwarded message ---------- > From: "[email protected]" <[email protected]> > To: "[email protected]" <[email protected]>, " > [email protected]" <[email protected]> > Date: Fri, 4 Mar 2011 15:57:54 -0500 > Subject: Re: [OSL | CCIE_RS] (ccie_rs) native vlan > Well vlan 1 by default carries all of the spannin tree messages and things > like that. Its basically the equivalent of 224.0.0.5 in OSPF. Its how the > switches communicate. Hopefully what I've said helps and someone else please > correct me if I'm wrong but this is how I understand spanning-tree > > Sent from my Verizon Wireless Phone > > > ----- Reply message ----- > From: "[email protected]" <[email protected]> > Date: Fri, Mar 4, 2011 1:54 pm > Subject: [OSL | CCIE_RS] (ccie_rs) native vlan > To: "[email protected]" <[email protected]> > > Hi > iread that native vlan is vlan 1 by default in switch but i want to know > that What does native vlan do? And what is importance it has? > And at last why should we not change native vlan for best practice? > > Regards > narendra > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > > > ---------- Forwarded message ---------- > From: cyrus riobah <[email protected]> > To: CC IE <[email protected]> > Date: Sat, 5 Mar 2011 01:50:54 +0300 > Subject: [OSL | CCIE_RS] hostname mismatch > Is it a mistake of switch hostname mismatch or there is something am not > getting here? > > Am currently sited on proctor session and what i can see from sh vl b on > the > pod is not what is on solution guide; Cat3560-3 on solution guide has vlan > that Cat3560-1 should have when sh vl b is done. > > Am i missing something here? > > Regards > > Cyrus > > > > ---------- Forwarded message ---------- > From: <[email protected]> > To: [email protected] > Date: Fri, 04 Mar 2011 15:59:14 -0700 > Subject: Re: [OSL | CCIE_RS] (ccie_rs)_native_vlan > Oops. Hit "Reply" instead of "Reply All." > > >Well vlan 1 by default carries all of the spannin tree messages and things > like that. Its basically the > >equivalent of 224.0.0.5 in OSPF. Its how the switches communicate. > Hopefully what I've said helps and someone > >else please correct me if I'm wrong but this is how I understand > spanning-tree > > Spanning tree BPDUs are actually layer 2, not layer 3. They are sent to > the L2 multicast address 01:80:C2:00:00:00. I believe that VLAN1 just > carries all traffic by default unless that traffic is tagged for another > VLAN (even supposing the native VLAN on, say f0/2 was VLAN3, if traffic > were to enter f0/2, it would be tagged as VLAN3 as it left f0/2 then > dealt with as necessary). > > I'm sure that the BPDU information is correct, and I _think_ the VLAN > info is as well, but I'm certainly open to correction if necessary. > > --jdguffey > > > > > ---------- Forwarded message ---------- > From: marc abel <[email protected]> > To: cyrus riobah <[email protected]> > Date: Fri, 4 Mar 2011 21:29:03 -0600 > Subject: Re: [OSL | CCIE_RS] hostname mismatch > There is not enough information here to even wager a guess. It could be you > have the hosts confused, it could be you have your vtp setup incorrectly, > it > could be any number of things. If you want an answer to a question like > this > you should include the lab and task # (if appropriate) and also some actual > show command output and better details. > > -Marc > > On Fri, Mar 4, 2011 at 4:50 PM, cyrus riobah <[email protected]> wrote: > > > Is it a mistake of switch hostname mismatch or there is something am not > > getting here? > > > > Am currently sited on proctor session and what i can see from sh vl b on > > the > > pod is not what is on solution guide; Cat3560-3 on solution guide has > vlan > > that Cat3560-1 should have when sh vl b is done. > > > > Am i missing something here? > > > > Regards > > > > Cyrus > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, please > > visit www.ipexpert.com > > > > > > ---------- Forwarded message ---------- > From: Michael Smith <[email protected]> > To: <[email protected]> > Date: Sat, 5 Mar 2011 00:24:17 -0500 > Subject: Re: [OSL | CCIE_RS] (ccie_rs)_native_vlan > > Well I know that spanning tree is layer 2 not layer three I was just making > a comparison. > I'm basically saying that all switch management traffic is sent over the > native vlan which is by default 1. > And OSPF sends out information to 224.0.0.5. It was probably a terrible > comparison but I'm just > trying to figure out a way to say basically the native vlan is what the > switches send traffic out on. > > > > > > From: [email protected] > > To: [email protected] > > CC: [email protected]; [email protected] > > Subject: RE: [OSL | CCIE_RS] (ccie_rs)_native_vlan > > Date: Fri, 4 Mar 2011 15:59:14 -0700 > > > > Oops. Hit "Reply" instead of "Reply All." > > > > >Well vlan 1 by default carries all of the spannin tree messages and > things like that. Its basically the > > >equivalent of 224.0.0.5 in OSPF. Its how the switches communicate. > Hopefully what I've said helps and someone > > >else please correct me if I'm wrong but this is how I understand > spanning-tree > > > > Spanning tree BPDUs are actually layer 2, not layer 3. They are sent to > > the L2 multicast address 01:80:C2:00:00:00. I believe that VLAN1 just > > carries all traffic by default unless that traffic is tagged for another > > VLAN (even supposing the native VLAN on, say f0/2 was VLAN3, if traffic > > were to enter f0/2, it would be tagged as VLAN3 as it left f0/2 then > > dealt with as necessary). > > > > I'm sure that the BPDU information is correct, and I _think_ the VLAN > > info is as well, but I'm certainly open to correction if necessary. > > > > --jdguffey > > > > > > ---------- Forwarded message ---------- > From: Michael Smith <[email protected]> > To: <[email protected]> > Date: Sat, 5 Mar 2011 00:41:15 -0500 > Subject: [OSL | CCIE_RS] Volume 2 lab 2 Task 9.1 > > Hello all, > > I came across a task that looks a little strange to me. Here is the > question: Vlan B should have no more than 2mb of throughput traffic. Vlan B > only exists on Cat 1 and is interface fa0/1 - 2. > My original config before looking at the ipexpert manual looks like this: > > mls qos > mls qos aggregate-policer TASK9.1 2000000 500000 exceed-action drop > policy-map TASK9.1 > class class-default > police aggregate TASK9.1 > > I applied the above config on the input side of the interfaces on the > switch. Do you guys think this config would actually work? Also when I > looked up the ipexpert answer it said basically the same > things but with these changes: > > class-map VLANB > match vlan 12 > match class-map class-default > policy-map VLANB > class VLANB > police aggregate VLANB > > Now when I attempted to emulate these configs on the switch I have here at > home this is what I showed: > > Cat4(config-cmap)#class-map TASK9.1 > Cat4(config-cmap)#match ? > access-group Access group > input-interface Select one or more input interfaces to match > ip IP specific values > > Here is the show version on my switch: > do sh ver > Cisco IOS Software, C3560 Software (C3560-IPSERVICESK9-M), Version > 12.2(55)SE1, RELEASE SOFTWARE (fc1) > Technical Support: http://www.cisco.com/techsupport > Copyright (c) 1986-2010 by Cisco Systems, Inc. > Compiled Thu 02-Dec-10 07:17 by prod_rel_team > Image text-base: 0x01000000, data-base: 0x02F00000 > > ROM: Bootstrap program is C3560 boot loader > BOOTLDR: C3560 Boot Loader (C3560-HBOOT-M) Version 12.2(44)SE5, RELEASE > SOFTWARE (fc1) > > Cat4 uptime is 48 minutes > System returned to ROM by power-on > System image file is "flash:c3560-ipservicesk9-mz.122-55.SE1.bin" > > > This product contains cryptographic features and is subject to United > States and local country laws governing import, export, transfer and > use. Delivery of Cisco cryptographic products does not imply > third-party authority to import, export, distribute or use encryption. > Importers, exporters, distributors and users are responsible for > compliance with U.S. and local country laws. By using this product you > agree to comply with applicable laws and regulations. If you are unable > to comply with U.S. and local laws, return this product immediately. > > A summary of U.S. laws governing Cisco cryptographic products may be found > at: > http://www.cisco.com/wwl/export/crypto/tool/stqrg.html > > If you require further assistance please contact us by sending email to > [email protected]. > > cisco WS-C3560G-24TS (PowerPC405) processor (revision D0) with 131072K > bytes of memory. > Processor board ID FOC1409Z1LY > Last reset from power-on > 2 Virtual Ethernet interfaces > 28 Gigabit Ethernet interfaces > The password-recovery mechanism is enabled. > > 512K bytes of flash-simulated non-volatile configuration memory. > Base ethernet MAC Address : 08:1F:F3:16:72:80 > Motherboard assembly number : 73-10215-04 > Power supply part number : 341-0098-02 > Motherboard serial number : FOC14092S4D > Power supply serial number : AZS140516QK > Model revision number : D0 > Motherboard revision number : F0 > Model number : WS-C3560G-24TS-S > System serial number : FOC1409Z1LY > Top Assembly Part Number : 800-26851-01 > Top Assembly Revision Number : E0 > Version ID : V03 > CLEI Code Number : CNMW200ARC > Hardware Board Revision Number : 0x09 > > > Switch Ports Model SW Version SW Image > ------ ----- ----- ---------- ---------- > * 1 28 WS-C3560G-24TS 12.2(55)SE1 C3560-IPSERVICESK9-M > > Now is there any reason why I wouldn't have these commands in my ios > version? Any help would be great! Sorry for the long winded email! > > > > > > ---------- Forwarded message ---------- > From: Kurt Bales <[email protected]> > To: [email protected] > Date: Sat, 5 Mar 2011 17:18:52 +1100 > Subject: Re: [OSL | CCIE_RS] (ccie_rs)_native_vlan > I also would like to point to a blog post that Marko wrote in Janurary > > http://blog.ipexpert.com/2011/01/19/old-ccie-myths-vlan-1/ > > While this is not specifically about native vlans, it does discuss how > certain protocols "that use vlan 1" are treated as unique cases when > trunking etc. > > Hope this helps, > > Kurt > @networkjanitor > > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
