If you only allow ONE MAC through a port I can't see how DHCPstarv is going to work (unless it is some kind of distributed DHCPStarv attack).
DHCPStarv works by sending a lot of DHCP petitions so that the server doesn't have new IPs to provide to new clients. But if you can only ask for one a time it is not likely the attack is going to succeed.
After @RajesK comment (he has found the link answering his own question) I add the following:
Although one might think that countermeasures such as as Port Security
would be more than enough to prevent such attacks, that is not true
with tools like Yersinia or dhcpstarv. This is because Port Security
only considers the MAC source of the frame to create filters and then
set accordingly what MAC addresses are allowed on a specific port
(useful against MAC flooding attacks). The problem here is that these
tools do not change this MAC (as eg macof does), but randomize the
field Client Hardware Address (CHADDR) inside the DHCP payload. This
field, along with the client identifier, is of great importance as it
will be used (see RFC 2131) by the server to distinguish between the
various requests of different customers. Without that, it would be
difficult to distinguish between the various users when using a DHCP
This means that the problem is that the DHCP protocol itself rely not on the MAC of the client who ask for the new IP but for the CHADDR field inside the DHCP protocol so, in fact, from the very same MAC you can ask for thousands of petitions just changing the CHADDR field.
The solution is in the very same link:
Fortunately, DHCP Snooping is clever enough to read the payload of the
DHCP protocol and verify that the source MAC address and CHADDR are
the same (optional command ip dhcp snooping verify mac-address). It is
also possible to set a “maximum threshold“, or number of packets per
second that the switch can receive in a given port so, if the number
of DHCP packets reaches this threshold, the port enters the shutdown
mode (blocking) and it would generate a warning about the DoS.
Now, you are comparing the actual MAC address with the one inside the DHCP protocol so that when you find a different one you just discard the packet.
Saying this you should continue bear in mind the comments by @polynomial.