|
|
 FAQ
 Search
 Memberlist
 Usergroups
 Register
 Profile
 Private messages
 Log in
|
|
| Author |
Message |
Guest
|
 Posted: Fri Aug 10, 2007 12:49 am Post subject: Native VLAN mismatch on Cisco 2950 |
 |
|
Little back ground:
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 |
|
| Back to top |
|
 |
|
|
Leander de Graaf
Guest
|
| Posted: Fri Aug 10, 2007 12:49 am Post subject: Re: Native VLAN mismatch on Cisco 2950 |
|
|
bavien@gmail.com wrote:
| Quote: | Little back ground:
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
If you are using dot1q as a trunking protocol (most common) you also |
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. |
|
| Back to top |
|
|
|
|
