I recently attended a training / multi-vendor class and had two claim that you can take the DHCP IP address that was given to you and make it static with no issues or conflicts. Any ideas or references to articles. Thank you.
I'd agree with U1 regarding this statement, that if you have access to configure the DHCP server or can have someone else change it readily as needed, it is generally preferable to keep all devices dynamic and assign reservations to them so that changes like gateway, DNS, etc. can propagate automatically. Note the bolded text, though: if you don't have the ability to update the DHCP server, or have it updated as needed, you could run into a problem in the process of setting things up.
With that in mind, I'll add another consideration here, in that handling of static addresses within the DHCP pool will vary depending on the DHCP server. I've had routers that nicely recognized when an address was in use and handily avoided giving it out in response to DHCP requests. I've seen others that will merrily give out the next available address whether something else has it statically already or not. Obviously the latter causes problems... the former, while not being ideal, doesn't.
With our main client, we've arranged a middle ground: where we used to multi-home the NIC in the DVR with both an assigned static IP on their 10.xx LAN, and a 192.168.2.xx IP for all our other equipment, they now have managed switches and firewalls on all their sites and give us our own VLAN for all our equipment, following the standard of 10.xx.1.* where xx is the site number. From there we devised a set of IP ranges to be used for all sites:
10.xx.1.20-39 is the DHCP pool available to the VLAN
10.xx.1.40 and .41 are for the DVRs/NVRs (some sites use two)
10.xx.1.45 is the management console on the RAID
10.xx.1.46 thru 49 are the iSCSI ports
10.xx.1.50 thru 59 are our managed switches (most sites only have one)
10.xx.1.60 thru 69 are video decoders (for public awareness monitors, usually)
10.xx.1.95 thru 99 are access control panels
10.xx.1.101 thru 132 are cameras on the first DVR/NVR, the IP corresponding to the channel
10.xx.1.201 thru 232 are cameras on the second DVR/NVR
All devices are statically assigned, with the DHCP pool being there mainly for initial setup of devices that default to DHCP (Advanced IP Scanner can then find them easily).
Other trades/technology areas have their own dedicated VLANs as well.
This works well because the guy who has the task of managing the VLANs isn't always available to add or change reservations for us (and the other trades), and certainly doesn't want to be spending all his time managing the reservation tables.