 sister, not to be offended in any manner). Python language is readily available source for coding here. To be clear in the language, the reference of the term NOX only refers to the original one and not the Classic (though they both are NOX) because there lies a certain amount of differences between both of them. Refer to Table 1 for clarity among the differences amongst the mentioned. NOX Architecture Figure 3 elucidates the architecture of NOX controller. Research by Sridhar Rao (2014) supports that the central core of NOX gives helper methods, like threading and event engine, along with network packet process apart from the OpenFlow API for communicating with the switches and input output support. The first layer of the architecture has Core, Net, Web apps. With the advancement of NOX architecture there are only 2 core applications, which include switch and OpenFlow. The network and web apps have been discontinued or let us say removed. The central layer has in-built components of NOX. The managers and dispatchers in the central layer are self-explanatory while the DSO i.e. the dynamic shared object scans the directory structure of any components being implemented as it is. Initiating NOX The presumptions are that you run on a terminal in a linux machine. To start or to initiate NOX, the command ine should be within "build/src" directory. The statement to initiate the NOX is somewhat like below mentioned: Table 1. NOX versions comparisons NOX Classic Internal Applications Simple Network Management Protocol OpenFlow, Switch Network Apps Authorising, Routing, Managing Web Apps Web server and various internet services Language(s) Available C++ and Python C++ Only Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 The Heart and Brain of SDN Figure 3. Architecture of NOX controller Core Apps Net Apps Web Apps NOX-Controller Connection Event Openflow DSO Deployer Existing Manager Dispatcher Manager Components Input/Output: Core Services: Socket Openflow Threading and Event Asynch