LockDown32
asked on
DHCP Reservations
It is a Windows 2012 Server running DHCP passing out IPs in the range 192.168.1.100-254
I am having trouble making a reservation at 192.168.1.4. Is that because it doesn't fall in the range of 100-254?
Kind of a awkward question....
I am having trouble making a reservation at 192.168.1.4. Is that because it doesn't fall in the range of 100-254?
Kind of a awkward question....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That is why it was an awkward question. In thinking about it logically it could go either way. The Reservation is done by the DHCP Server but that doesn't necessarily equate to it having to be in the scope range. The reason is stupid anyway. A screw up by HPE on their 19XX and 16XX series switches. They put all these neat NTP features in but but forgot to put a place in the GUI to set gateway address. Oops! The NTP works if you let it go DHCP but I like knowing where my switches are. Usually static IP them. Hence the shot at a reservation. HPE has been living off their name for way too long. Even if you look at the MAC Address (Unique ID) that the DHCP Server picks up it is always like 23412412953987238579893257 68235525 and when you try to turn it in to a reservation it gives you the warning that the MAC address isn't standard and asks if you want to use it anyway. HPE says they can get a reservation to work. I can't. The only difference I can see is that my reservation is outside the scope. It works when it was inside the scope.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I love using static IP addresses. That is the way it should be but as mentioned above when I use a static IP address there is no place to put a gateway address and as a result none of the NTP functions work because without a gateway address the switch has no internet. I don't know what HPE was thinking. Obviously they weren't.....
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes. A total bonehead move. I opened a case with HPE a year ago and there response was "we are trying to make a low cost switch and had to omit that feature" yet they put stuff in for Daylight Savings, NTP and the rest. There are ways to do it:
On both the 1920 and 1620 you can use the console cable and set the gateway via the CLI but how inconvenient is that? Serial ports went out with mini skirts back in the 70s.
On the 1920 you can telnet to it and set it with the CLI or use a static route.
They had room to put in this real annoying captcha verification when you log in to the switch but didn't have the room to set a gateway address? Kind of like Symantec. They have been living off their name way too long. Maybe it is time to change things up.
On both the 1920 and 1620 you can use the console cable and set the gateway via the CLI but how inconvenient is that? Serial ports went out with mini skirts back in the 70s.
On the 1920 you can telnet to it and set it with the CLI or use a static route.
They had room to put in this real annoying captcha verification when you log in to the switch but didn't have the room to set a gateway address? Kind of like Symantec. They have been living off their name way too long. Maybe it is time to change things up.
You should be able to change the DHCP range to the full network, then exclude the range up to 99, and then do a reservation.
ASKER
For the record the Reservation outside the scope did work. I must have pulled an HPE when I tried it the first time. Something that document says shouldn't work in 2012 R2 but does. The actual MAC address is 356338612e333836342e346438 342d566c61 6e2d696e74 6572666163 6531 can you believe that? Maybe I did a type the first time.
Rather then jumping through all these hoops it sure seems like the simple approach would be for them to add a place to set a gateway address in the GUI but what do I know? Thanks guys....
Rather then jumping through all these hoops it sure seems like the simple approach would be for them to add a place to set a gateway address in the GUI but what do I know? Thanks guys....
Thank you and good luck here.
ASKER