Skip to main content

DHCP Dora process

DORA in simple words is the process through which a DHCP client acquires an IP address from a DHCP server in the network

D- Discover: When a machine boots up in lan and it doesnt have an IP address configured , it would send a DHCP discover broadcast to the network. It will have a destination IP of 25.255.255.255. It also includes it mac address encapsculated in the package. The layer 2 destination would be ff:ff:ff:ff:ff:ff, ie to add devices in the network. The switch port which received the package would then forward it to all other ports in the switch except on the one from which the request is received.

O- Offer: If there is a dhcp server listening on the network, it will respond back to the DHCPrequest package with an offer package. The offer package is again a broadcast to 255.255.255.255, but it will have the destination mac address set to the DHCP client's mac address. The source mac address will be that of the DHCP server. The offer package will contain the IP address,DNS,gateway etc as well

R- Request: The dhcp client will get similar offers from all dhcp servers in the network and it will typically accept the first one that it receives.It will then send a request to the DHCP for the offered IP address.

A-Acknowledge: When DHCP received the DHCp Request from the client for the IP address, it will send back a DHCP aknowledge, thereby allocating that IP address to the client

Comments

  1. The DORA process are a part of the client message from the DHCP protocol perspective.In which only clients that are willing to request an IP address send these messages.

    Thanks
    Silvester Norman

    Change MAC Address

    ReplyDelete
    Replies
    1. You are right Silvester. Only if the client is configured to obtain IP address automatically(that is, from DHCP), this process will be initiated

      Delete
  2. Is the above information correct about the Dora process ?

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows server 2012: where is my start button??

If you have been using Windows Server OS for a while, the one thing that will strike you most when you login to a Windows server 2012 is that there is no start button!!.. What??..How am I going to manage it?? Microsoft feels that you really dont need a start button, since you can do almost everything from your server  manager or even remotely from your desktop. After all the initial configurations are done, you could also do away with the GUI and go back to server core option.(In server 2012, there is an option to add and remove GUI). So does that mean, you need to learn to live without a start button. Actually no, the start button is very much there .Lets start looking for it. Option 1: There is "charms" bar on the side of your deskop, where you will find a "start" option. You can use the "Windows +C" shortcut to pop out the charms bar Option 2: There is a hidden "start area"in  the bottom left corner of your desktop

Install nested KVM in VMware ESXi 5.1

In this blog, I will explain the steps required to run a nested KVM hypervisor on  Vmware ESXi. The installation of KVM is done on Ubuntu 13.10(64 bit). Note: It is assumed that you have already installed your Ubuntu 13.10 VM in ESXi, and hence we will not look into the Ubuntu installation part. 1) Upgrade VM Hardware version to 9. In my ESXi server, the default VM hardware version was 8. So I had to shutdown my VM and upgrade the Hardware version to 9 to get the KVM hypervisor working. You can right click the VM and select the Upgrade hardware option to do this. 2)In the ESXi host In /etc/vmware edit the 'config' file and add the following setting vhv.enable = "TRUE" 3)Edit the VM settings and go to VM settings > Options  > CPU/MMU Virtualization . Select the Intel EPT option 4) Go to Options->CPUID mask> Advanced-> Level 1, add the following CPU mask level ECX  ---- ---- ---- ---- ---- ---- --H- ---- 5) Open the vmx

Virtual fibre channel in Hyper V

Virtual fibre channel option in Hyper V allows the connection to pass through from physical  fibre channel HBA to virtual fibre channel HBA, and still have the flexibilities like live migration. Pre-requisites: VM should be running Windows Server 2008, 2008 R2 or Windows Server 2012 Supported physical HBA with N_Port Virtualization(NPIV) enabled in the HBA. This can be enabled using any management utility provided by the SAN manufacturer. If you need to enable live migration, each host should be having two physical HBAs and each HBA should have two World Wide Names(WWN). WWN is used to established connectivity to FC storage.When you perform migration, the second node can use the second WWN to connect to the storage and then the first node can release its connection. Thereby the storage connectivity is maintained during live migration Configuring virtual fibre channel is a two step process Step 1: Create a Virtual SAN in the Hyper-V host First you need to click on Virtual