How do you allocate Internet Protocol Suite addresses in your network?

In the IP addressing world, know your 'IP Versions' like a tech sommelier. IPv4 offers classic compatibility, while IPv6 serves the future vintage. Blend them wisely for a network that ages well and tastes of seamless connectivity.

Firstly to consider is IP address space is public or private. Public IP space depends on which IP address ranges you have leased. Private IP space allocate IP addresses to your devices per technology or per network part and also for end user devices. If those IP ranges are almost used you need to consider using IPv6 addressing in you network. Using smaller or larger IP pools depends on how operator is prepared to use second or third ip pool as addition to the first. Otherwise IP addresses from large IP pools might be dedicated but not used which is waste of IP addressing resources.

First i will assign an IP address to the device. This IP can be an IPv4 address or IPV6 address. I will define what will be its subnet mask for this address space.

I will check how many devices are in my network. Denpedning upon the number of devices i will assign subnet mask for this prefix. If we have 6 hosts in our network then i will provide /29 subnet mask.

I will define planned IP address on router interface. One IP will be configured on router link and other will be on computer machine.

I will manage a record for all host machine IP addresses. I will link this IP address with a specific name by using Domain Name Server (DNS)

Before you starting troubleshoot, you need make sure you’re very confortable with the differences between IPv4 and IPv6 in terms of operation. For example, some protocols work differently (or with other approaches) when configured on IPv6 networks – for instance, you don’t have address-resolution protocol (ARP) anymore, then, you also need to have deeply understood of ICMPv6 and Neighbor Discovery Protocol (NDP) to gather the same information that you had obtained with ARP while using IPv4. Additionally, you need to know how to work with different type of addressing like ULA, LL, GU on Multicast/Unicast and now the new type: Anycast. Be positive, if there is no ARP anymore, the switch also had to learn another way to forward packets :D

I will check all the interface links are up and fine. IP address are acuratly assigned to each and every interface of machines.

Test of your network is one thing and troubleshooting is something other. In test usually you add new network device or new service/functionality/connectivity on existing. It starts with do I have right subnet, do other network devices use some IP addresses from my dedicated subnet. Then test checks for physical connectivity between devices and test of line protocols from both sides. And finally checks for type of connection and their durability. When comes to troubleshooting you have to thing other way. You need to see where you are in the network, is it core network is it access network or end user device. Do I check just network connectivity or I do some plus test for confirming customer service etc. Limit here is 750 characters :)

I will review and optimize network by using several techiniques. I will use a firwall to filter out any unauthorized traffic in to the network

This requires a detailed study of many factors in a Service Provider Network applicable to an Enterprise network. How many users? Sessions per user? NATing , IPv4/v6 Current Utilization? Prediction of User, No. Session growth Infrastructure Design and Capacity +Other factors