From: Abraham, Ajith (Ajith.Abraham@xxxxxxxxxx)
Date: Wed Aug 21 2002 - 14:15:41 GMT-3
The 2950's IOS by default use only dot1q. Cisco is moving in the standards
direction.
-----Original Message-----
From: Phil [mailto:ciscostudent1@yahoo.com.br]
Sent: Wednesday, August 21, 2002 11:57 AM
To: Chuck Church; 'ccielab@groupstudy.com'
Subject: Re: OT: Strange DHCP result with MSFC2
Chuck,
Did you change the Native Vlan for all trunks to Vlan99? I don't know if
this would help though.
Just curious, Why are you using DOT1Q? Is there any non-Cisco equipment
involved?
Phil
Chuck Church <cchurch@MAGNACOM.com> escreveu: All,
I've just completed an install of a MSFC2-equipped 6509 with many
3500XLs hanging off. DOT1Q trunks everywhere. The user VLANs are 1 and 3
(not my idea to use 1, legacy thing). The management VLAN is 99 for all the
3500s. The MSFCs routes all VLANS. I had configured a DHCP pool on the
MSFC2 for VLAN 99, as each workgroup switch has a VLAN 99 port for techs to
use in the closet, as VLAN 99 is blocked via ACL from the user VLANs.
Anyway, to make a long story short, I was getting VLAN 99 addresses via DHCP
on VLAN 1, which was reeking havoc as you can imagine. 'Sh ip dhcp bind'
proved they were coming from the MSFC2. I've read that internally the MSFCs
use ISL, while outside I'm using DOT1Q. Is it possible that the tagging and
untagging of VLAN 1 (difference between ISL and DOT1Q) is getting confused
somewhere? I didn't see anything on CCO about it. The Sup is running 6.3.7
CatOS, the MSFC is 12.1.11-E4. Any ideas? We're considering creating a new
VLAN and not using 1, but only if there's no easy solution. Maybe tagging
VLAN1, making something else native? My pool was basic, with the correct
network statement and a default gateway.
Thanks,
Chuck Church
CCIE #8776, MCNE, MCSE
Sr. Network Engineer
Magnacom Technologies
140 N. Rt. 303
Valley Cottage, NY 10989
845-267-4000
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:32 GMT-3