|
|
|
Bookmark this page:
Yahoo!
Windows Live
del.icio.us
digg
Netscape
|
|
|||||||||||||||||||
|
Posted by on August 9, 2007, 6:30 pm
Please log in for more thread options
Currently we have a Cisco 3750 and a couple of Cisco 2950 switches. Only one VLAN on the whole network and that is the default VLAN 1 out of the box. I want to create an additional VLAN for management so that in the end there will be two VLANs, one for management and one for user. My questions are: 1. Any benefit/reason in using VLAN 1 for management and create another VLAN for users compare to using VLAN 1 for users and create another VLAN for management? 2. I did some test and set all the ports in one of the 2950 to VLAN 10. Configure fa0/24 on the 2950 for trunking to Cisco 3750. Got Native VLAN mismatch warning when issuing "show interface trunk" on the 2950. Does this message indicates something is wrong or we can have mismatch native vlan? Thanks... BV | |||||||||||||||||||
|
Posted by Leander de Graaf on August 9, 2007, 7:19 pm
Please log in for more thread options need to configure the same native VLAN on both ends of the trunk, as the packets of that VLAN are send untagged. use interface config command "switchport trunk native vlan vlan-nr" to change the specific VLAN on one or both sides. This probably is the cause of the native VLAN mismatch you are experiencing. And yes, it can be a good practice to seperate management and users VLANs, though its not a requirement. | |||||||||||||||||||
|
Posted by Arthur Brain on August 10, 2007, 4:16 am
Please log in for more thread options
bav...@gmail.com wrote: > 2. I did some test and set all the ports in one of the 2950 to VLAN
> 10. Configure fa0/24 on the 2950 for trunking to Cisco 3750. Got > Native VLAN mismatch warning when issuing "show interface trunk" on > the 2950. Does this message indicates something is wrong or we can > have mismatch native vlan? You can have it. It just means that, on the trunk between them, your 3750 is treating un-tagged frames as though they were VLAN 1, and your 2950 is treating un-tagged frames as VLAN 10. Basically a sign of poor design, but not *necessarily* of any problem. | |||||||||||||||||||
|
Posted by Arthur Brain on August 10, 2007, 9:12 pm
Please log in for more thread options
Arthur Brain wrote: > bav...@gmail.com wrote:
> > > 2. I did some test and set all the ports in one of the 2950 to VLAN
> > 10. Configure fa0/24 on the 2950 for trunking to Cisco 3750. Got > > Native VLAN mismatch warning when issuing "show interface trunk" on > > the 2950. Does this message indicates something is wrong or we can > > have mismatch native vlan? >
> You can have it. > > It just means that, on the trunk between them, your 3750 is treating > un-tagged frames as though they were VLAN 1, and your 2950 is treating > un-tagged frames as VLAN 10. > > Basically a sign of poor design, but not *necessarily* of any problem. Actually, I was just playing with an old 3548 switch, patched to a trunk port on a 3750 and the 3548 was actually disabling ports where a VLAN mismatch was detected. | |||||||||||||||||||
|
Posted by on August 10, 2007, 9:52 pm
Please log in for more thread options > Arthur Brain wrote:
> > bav...@gmail.com wrote:
>
> > > 2. I did some test and set all the ports in one of the 2950 to VLAN
> > > 10. Configure fa0/24 on the 2950 for trunking to Cisco 3750. Got > > > Native VLAN mismatch warning when issuing "show interface trunk" on > > > the 2950. Does this message indicates something is wrong or we can > > > have mismatch native vlan? >
> > You can have it.
>
> > It just means that, on the trunk between them, your 3750 is treating
> > un-tagged frames as though they were VLAN 1, and your 2950 is treating > > un-tagged frames as VLAN 10. >
> > Basically a sign of poor design, but not *necessarily* of any problem.
>
> Actually, I was just playing with an old 3548 switch, patched to a > trunk port on a 3750 and the 3548 was actually disabling ports where a > VLAN mismatch was detected.- Hide quoted text - > > - Show quoted text - On the 2950 with all ports on VLAN10, I changed port 1 to access mode 1 (default VLAN), connect a PC to port 1 and found out that the PC cannot see any devices on the 3750 switch (which all ports default to VLAN1) BV | |||||||||||||||||||
| Similar Threads | Posted |
| Native VLAN mismatch on Cisco 2950 | August 9, 2007, 6:30 pm |
| Native Vlan Mismatch error | January 20, 2008, 2:09 am |
| Native Vlan Cisco 1200 Access Point | March 11, 2006, 7:50 pm |
| Native, and management vlan "Vlan 1" | September 21, 2005, 2:50 pm |
| VLAN Project and Native VLAN | July 13, 2007, 5:06 am |
| Native VLAN | February 8, 2007, 9:40 pm |
| native vlan | December 18, 2008, 6:45 am |
| Native VLAN Warning | August 23, 2005, 8:24 am |
| understanding native VLAN | September 23, 2005, 10:10 pm |
| Native VLAN question | November 22, 2005, 5:58 am |
| native vlan question | April 15, 2008, 3:51 am |
| native vlan for mgmt | July 18, 2009, 9:20 pm |
| Change native VLAN on ASA 5520 | July 5, 2007, 6:17 am |
| change native vlan globaly on 3560 | January 5, 2007, 2:08 pm |
| Changing native vlan on access port | August 12, 2009, 6:53 pm |

Native VLAN mismatch on Cisco 2950
Yahoo!
Windows Live
del.icio.us
digg
Netscape 







>
> Currently we have a Cisco 3750 and a couple of Cisco 2950 switches.
> Only one VLAN on the whole network and that is the default VLAN 1 out
> of the box. I want to create an additional VLAN for management so that
> in the end there will be two VLANs, one for management and one for
> user. My questions are:
>
> 1. Any benefit/reason in using VLAN 1 for management and create
> another VLAN for users compare to using VLAN 1 for users and create
> another VLAN for management?
>
> 2. I did some test and set all the ports in one of the 2950 to VLAN
> 10. Configure fa0/24 on the 2950 for trunking to Cisco 3750. Got
> Native VLAN mismatch warning when issuing "show interface trunk" on
> the 2950. Does this message indicates something is wrong or we can
> have mismatch native vlan?
>
> Thanks...
>
> BV
>