gle's internal network ran entirely on OpenFlow. Secure Channel A brief look at the specification of OpenFlow shows the single point where the forwarding plane and control plane are connected. It is the secure channel between the controller and the switch. If the connection to the controller is lost, a pure Openflow switch will not be able to deal with unknown incoming packets. The secure channel is the lifeline of all Openflow switches in SDN. It is a TLS or TCP connection established between the controller and the switch. If the connection is lost, the switch will try to connect to a backup controller if there is one. This is the "fail secure mode" and all packets to the controller will be dropped. In an Openflow switch, all new packets will be processed in the switch and will not be sent to the controller. If the switch is capable of working both in SDN and in none SDN then, it is called Hybrid switch. In this case, the switch will not follow the Openflow protocol and the network loses its SDN architecture. The Openflow specification shows that without a controller in the network, we are dealing with a non-SDN network with no central control or separation of forwarding and control plane (Wang A, Guo Y, Hao F, et al. (2013)),. This section shows the importance of detecting any threat that can make the controller unreachable. Downloaded 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Analysis of Issues in SDN Security and Solutions Simulation In order to find the output for the implementation and simulation of the model following command need to be executed in order to take ssh login. ssh -X mininet @172.16.32.128sudo mn -top tree, 3 - controller=remote, ip=192.168.43.130, port=6653 switch=ovsk, protocols=OpenFlow13 pingall In this case we had considered various cases while comparing our result. The first output will be for the normal traffic, where each host will have same probability of numbers of packets. This case was considered with total of 120 packets with a window. On simulatin