LockDown32
asked on
Problems with DHCP Reservation
It is a 2012 Server. I had an HP switch static IPed at 192.168.1.4 and good old HP decided not to put a place on the switch for a gateway address. It is a newer switch. A 1620. They put a place for a NTP Server and Daylight Savings Time they just "forgot" that NTP won't do any good with being able to set a gateway address for the internet. Oops!
Anyway... I think if will work if you let the switch go DHCP so I was trying to set up a reservation in the DHCP Server on the Server. I don't do a lot with reservations. I got the MAC address of the switch and set up a reservation to put it right back at 192.168.1.4 but it isn't working,
On the DHCP Server it simply says Reservation (inactive). The DHCP Server is passing out 100-254 so putting a reservation outside that scope is OK isn't it? How do you debug the fact that it isn't working.
Anyway... I think if will work if you let the switch go DHCP so I was trying to set up a reservation in the DHCP Server on the Server. I don't do a lot with reservations. I got the MAC address of the switch and set up a reservation to put it right back at 192.168.1.4 but it isn't working,
On the DHCP Server it simply says Reservation (inactive). The DHCP Server is passing out 100-254 so putting a reservation outside that scope is OK isn't it? How do you debug the fact that it isn't working.
An obvious question I know, but you have changed the switch setting back to DHCP haven't you?
ASKER
Always start with "Is it turned on" :) Yes. I can see it in the DHCP Server under address leases. Can't figure it out. I pinged the switch and then did a arp -a to verify the MAC address. I don't do much in the way of reservations but it looked so simple. I have to be missing something obvious.
ASKER
I found the switch under Address Leases and the "Unique Identifier" is 356338612e333836342e346438 342d566c61 6e2d696e74 6572666163 6531
That isn't even close to the MAC address
That isn't even close to the MAC address
I'm not sure that I've understood you. Can you confirm that you're still seeing the reservation as inactive? If so, if you haven't put too much configuration on the switch, it might be worth factory resetting it. It will then revert to DHCP and it will either pick up the reservation if you have recorded the MAC correctly. If you haven't then you should be able to find whatever lease it has picked up on the DHCP server.
ASKER
I have never seen the Reservation go Active. I can see the switch under address leases. It is picking up a DHCP but not the Reservation. That is where I see the "Unique Identifier" as 356338612e333836342e346438 342d566c61 6e2d696e74 6572666163 6531
I cycled power to the switch. No joy. I will try a factory reset tomorrow and let you know what happens.....
I cycled power to the switch. No joy. I will try a factory reset tomorrow and let you know what happens.....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I've just double checked what I've just advised you of and when converted the string reads: 5c8a.3864.4d84-Vlan-interf ace1. A little more familiar.
ASKER
Thanks David but I am not sure where that leaves us. You want me to put that in the reservation as a MAC address instead of 356338612e333836342e346438 342d566c61 6e2d696e74 6572666163 6531 ?
That was more to make sense of what you were seeing. I would have hoped that you could still use the ascii reference, but if not the hex string may be useable. In the first instance could you confirm the MAC address that you originally entered into the reservation that you created?
ASKER
Yes. As mentioned above I dropped to a command prompt, pinged it and then did a arp -a and verified the MAC address. It was the same as what I saw in the firmware of the switch. I have a couple of these out in the field. Let me turn another one to DHCP and see what shows up as the UniqueID on the server.
ASKER
HPE really screwed the pooch on their latest Web Managed switches. I opened up a case with HPE. They spent a couple hours doing nothing more than we did above and decided to kick it up to tier 2....... oops!