4510 R+E Sup 8E Static IP Strange Behavior

[Ryan Curry]

OK all, there's a half-eaten four pack of chicken nuggets if you can help me figure this one out.  We have our first 4510 with a Sup8 (running version 03.03.00.XO.151-1.XO) running in an IDF.  Since we put it in, we've noticed that any Windows device that has a static IP address set will, on reboot, come up with a 169.x.x.x address (the Microsoft "I can't find a DHCP server address).  What's odd is that on the next reboot, it'll come up just fine.  So far I haven't found any bugs noting this issue but I wanted to see if anyone in the community has experienced this as well.  I'm thinking it may be a timing issue but even that I'm at a loss on.

Again, that's chicken nuggets.

Thanks all!

[Reza Sharifi]

If this was working with other sups and only happening after you upgraded to sup8, than I would start by upgrding the IOS version. What happens when you connect the same server to a different switch?

HTH

[casa_far · Accepted solution]

I recently faced to this strange behavior and I'm going to solve ...hoepfuly ;-) ... with this solution:

http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/8021x/116529-problemsolution-product-00.html

https://supportforums.cisco.com/discussion/11960461/ip-device-tracking

It seems a default behavior introduced with the ios 15.x and the win2008/win7 in conjunction with the avoid duplicate ip address mechanism.

If help please rate !

Good Luck 

[Ryan Curry]

Francesco, this is exactly what I needed.  I used the first solution and with extensive testing can say that it fixed my problem.  You, my friend, are a Godsend - just tell me where to send these chicken nuggets ...

[casa_far]

Happy to know It helped!

P.S.

Unfortunately the chicken would arrive cold :( but I appreciate the thought