There's a bug in Cat IOS code 12.1.4 (I think) which can cause the
problems you're mentioning. Did you try an upgrade?
The bug ID is CSCds89040 and it's related to HSRP configs and IOS
12.1(4)E. The bug prevents the correct MLS flows from being created.
An IOS upgrade fixed my similar problem right away.
Vijay Ramcharan
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Jeroen Timmer
Sent: Thursday, May 31, 2001 6:15 AM
To: [EMAIL PROTECTED]
Subject: RE: Weird DHCP/VLAN solution suggestions wanted!! [7:6579]
We did everything you described below .. We sniffered the network, we
saw that the client didn't get a reply from the DHCP server.
But what the cause is that the client doesn't get a reply .. We couldn't
find out. We also tried to release the client's ip address by ipconfig
/release etc. etc. This also didn't work, I had to delete the client in
the DHCP scope of NetID (where I found that client with his old ip
address and sometimes had to remove it several times) to let the client
get a new ip address by releasing his old ip address.
We used the NetID server for DHCP, even changed to a WinNT server to do
DHCP, but the problem still remains.
The thing we have configured in the router is only an ip-helper address
on each VLAN interface. What about the ip dhcp-server command ... Do you
have to configure that one to ?
With kind regards,
Jeroen Timmer
-----Original Message-----
From: Charles Manafa [mailto:[EMAIL PROTECTED]]
Sent: donderdag 31 mei 2001 11:47
To: [EMAIL PROTECTED]
Subject: RE: Weird DHCP/VLAN solution suggestions wanted!! [7:6579]
Try using DHCPLOC to monitor DHCP requests/replies traffic. This will
give you an indication as to why clients can not lease IP addresses.
I believe the reason why clients that move from one VLAN to another keep
getting the same IP address is because they are trying to renew the
existing IP address. Those clients need to release their IP addresses
before attempting to obtain a new one: IPCONFIG /RELEASE; IPCONFIG
/RENEW
CM
> -----Original Message-----
> From: Jeroen Timmer [mailto:[EMAIL PROTECTED]]
> Sent: 31 May 2001 10:03
> To: [EMAIL PROTECTED]
> Subject: RE: Weird DHCP/VLAN solution suggestions wanted!! [7:6579]
>
>
> We have a configuration at our company that has the same configuration
> as you just described.
> But somewhere along the line .. This doesn't seem to work that well.
>
> We got about 4 vlans, all vlan interfaces have an ip helper address to
> our DHCP server. Problem is that 8 out of 10 times, a DHCP client
> doesn't get an
> ip address. We used an Windows NT server as DHCP but also
> Nortel's NetID.
> Both systems give the same problems.
> Some times a user moves from one vlan to the other but gets
> an ip address
> from the old vlan he was in before he did a DHCP request for
> his new VLAN.
>
> We have been trying to find the solution but didn't succeed sofar,
> maybe somebody had this before and is willing to share it with me.
>
> We use a Cisco cat 6500 to handle to forwarding to the DHCP server and
> the VLAN routing, as access switches we have Cisco cat 3500.
>
>
> Thnx in advance,
>
> JT
>
> -----Original Message-----
> From: Pawel Sikora [mailto:[EMAIL PROTECTED]]
> Sent: donderdag 31 mei 2001 10:49
> To: [EMAIL PROTECTED]
> Subject: Re: Weird DHCP/VLAN solution suggestions wanted!! [7:6579]
>
>
> ----- Original Message -----
> From: "Sam Deckert"
>
> > The problem is the client wants to use DHCP, so that people in the
> > offices can simply plug in and away they go. But how would you go
> > about implementing a DHCP server in this situation?? In order to
> > allocate an address from the appropriate range, the DHCP
> server needs
> > to be aware of
> the
> > VLAN that the client DHCP request came from. I have not
> been able to
> > find
> a
> > DHCP server that has this capability whatsoever. I am sure
> this has
> > been done before - does anyone know how or have any suggestions??
>
> At the edge of each VLAN, an instance
> of router subinterface is obviously needed.
> You can configure at each subinterface
> ip helper address pointing to a real dhcp
> server located anywhere.
> Router then forwards any dhcp requests
> broadcasted by stations in vlans with
> apopriate subnet info, that dhcp server can
> use a defined scope for each vlan.
> Server than answers with lease data to the
> requestor via directed broadcast.
> (im not sure if such way)
>
> For example NT dhcp server service
> works flawlessy with such topology,
> with many different scopes.
>
> Pawel/
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=6603&t=6579
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
